|
BugTraq
MS to stop allowing passwords in URLs Jan 28 2004 10:54PM McAllister, Andrew (McAllisterA umsystem edu) (10 replies) Re: MS to stop allowing passwords in URLs Feb 03 2004 10:12PM Nick FitzGerald (nick virus-l demon co uk) RE: MS to stop allowing passwords in URLs Feb 03 2004 03:54PM Richard M. Smith (rms computerbytesman com) RE: MS to stop allowing passwords in URLs Feb 03 2004 02:26PM Andrew Harwood (aaharwood_maillist bigpond com) Re: MS to stop allowing passwords in URLs Feb 03 2004 04:01AM Dave Warren (dave warren devilsplayground net) (3 replies) Re: MS to stop allowing passwords in URLs Feb 06 2004 04:01AM Nick FitzGerald (nick virus-l demon co uk) Re: MS to stop allowing passwords in URLs Feb 03 2004 06:09PM David B Harris (dbharris eelf ddts net) RE: MS to stop allowing passwords in URLs Feb 03 2004 01:58AM Fergus Brooks (fergusb evolve-online com) (1 replies) |
|
Privacy Statement |
[ MS about to invalidate usage of http://<user>:<pass>@<host> in IE ]
> Anyone have any comments regarding legitimate uses of this syntax and
> Microsoft removing it from their browser? (and presumably the OS since
> the browser IS the OS).
There is no legitimate use of this syntax and never was. Although
RFC 2396 does specify a generic URI syntax allowing
<user>:<pass>@<host>:<port>
it expressly excludes those URLs whose syntax is specified in RFC 1738:
| This document updates and merges "Uniform Resource Locators" [RFC1738]
| and "Relative Uniform Resource Locators" [RFC1808] in order to define
| a single, generic syntax for all URI. It excludes those portions of
| RFC 1738 that defined the specific syntax of individual URL schemes;
| those portions will be updated as separate documents, as will the
| process for registration of new URI schemes.
RFC 1738 clearly says:
| An HTTP URL takes the form:
|
| http://<host>:<port>/<path>?<searchpart>
So do RFCs 1945 and 2616.
Regards
Ansgar Wiechers
[ reply ]