- From: Richard Gray <rlgray@us.ibm.com>
- Date: Tue, 6 Jan 1998 10:24:21 -0500
- To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
I am having some problems in finding appropriate documentation on how the HTTP 1.1 MUST requirement for absolute URI is implemented when using secure sockets layer (SSL). The question is what I should expect as an origin server in the absolute URL. The href in the HTML document the origin server sends to the browser would typically have an https://hostname/path coded to indicate to the browser to use SSL, but what is the absolute URL that the origin server would receive in this case? Is it: ...... http://hostname/path or : ..... https://hostname/path If the href were coded as http://hostname:443/path, it would be unambiguous. If it is https that would be received, then I hope we can add such a comment to the HTTP RFC, or else clarify that in the URL replacement RFC. Thank You, Richard Gray
Received on Tuesday, 6 January 1998 07:27:52 UTC