The VideoLAN Forums

Hi,

Why, when password protection on the VLC http interface was introduced, was a blank username chosen? This makes it almost impossible to access status.xml from a lot of script code. If an arbitrary username had been chosen (e.g. vlc) or the username was just plain ignored, it would cause a lot less code to choke AND would have allowed the use of a URL embedded username and password to allow access e.g.:

http://vlc:mypassword@localhost:8080/re ... status.xml

rfc1738 does not allow:

http://:mypassword@localhost:8080/requests/status.xml

This is very frustrating and potentially means I will have to either hack javascript framework I am using or change frameworks.

Stephen Parry

Originally, the HTTP interface supported arbitrary pairs of username and password. Since the developer that migrated the HTTP interface to Lua, thus removing usernames and passwords has long since left, nobody can answer your question.

FWIW, passing usernames and passwords through URL has been deprecated by RFCs for a number of years.

Hi

Has there been any development on this?

I'm stuck using version 2.0 because none of the methods I use to remotely access VLC work without a username.