Re: HTTPS and user:pass@site URI schemes

* Olivier Thereaux wrote:
>On Tuesday, Aug 5, 2003, at 21:36 Asia/Tokyo, Armin Herbert wrote:
>> I wanted to validate the contents of a page to which I can only connect
>> through an URI of this form:
>> https://user:password@www.example.com:80/foo/bar.html
>>
>> I can understand you don't want to support the user:pass@site scheme ..
>> it's not a (proposed) standard of any kind, if I'm right (please 
>> correct
>> me, if not).
>
>It is standard. At least, if I remember correctly, it's in the URI RFC.

RFC 1738:

   An HTTP URL takes the form:

      http://<host>:<port>/<path>?<searchpart>

   where <host> and <port> are as described in Section 3.1. If :<port>
   is omitted, the port defaults to 80.  No user name or password is
   allowed.

Similar for RFC 2616 and RFC 2818 for that matter. Not allowed.

Received on Thursday, 7 August 2003 06:31:23 UTC