I need to give an answer to our browser implementors. My understanding of the situation is: 1) In HTTP/1.1 HOST will be a required header field for http: URI's. 2) There is not portable way to easily guarantee that a client (on all platforms) can get a fully qualified domain name (fqdn) to place in HOST. So, is it acceptable for the client to place whatever it finds between the // and the first / in the HOST field, with the understanding it may not be a fqdn? If we can get a resolution on this soon, the addition of the HOST header will make the next Mosaic release. -- Elizabeth(Beth) Frank NCSA Server Development Team efrank@ncsa.uiuc.eduReceived on Thursday, 5 October 1995 09:25:16 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:42:56 UTC