Re: [tcpm] Comments on Soft Errors I-D: draft-ietf-tcpm-tcp-soft-errors-06

At Monday 02/07/2007 19:17 -0700, Joe Touch wrote:
>Lloyd Wood wrote:
>> At Monday 02/07/2007 13:13 -0700, Joe Touch wrote:
>>> There are exceptions, such as
>>> where multiple IP addresses are used for shared web service -- though
>>> that has fallen out of use as newer HTTP protocols determine the host in
>>> the request (sending GET and the DNS name, in addition to the filename)
>>> rather than only by the IP address (which was the only way compatible
>>> with HTTP 1.0, e.g.).
>> 
>> Care to elaborate?
>> 
>> Your claims don't match what e.g. RFC1945 specifies, or what HTTP 1.0 did.
>
>In 1.0 http://www.abc.com/ means
>        open a connection to an IP address www.abc.com resolves to
>        then issue "GET /"
>
>In 1.1, the same URL means
>        open a connection to an IP address www.abc.com resolves to
>        then issue "GET / HTTP/1.1 HOST: www.abc.com"
>
>This helps when www.abc.com and www.def.com are on the same host. In
>1.0, they had to have different IP addresses*, with servers listening on
>port 80 specific to those IP addresses. The address isn't actually sent
>(sorry that it was implied above).
>
>*(they could have different ports, but I'm focusing on the common case
>where the port isn't specified, e.g., for common public servers)
>
>In 1.1, you could have a single server listening on both IP addresses,
>with each HOST name bound to a different file root. The HOST option
>could indicate which DNS name's root to use.

Yes, the resolved IP address is never sent (unless it's already in the url.)

In http 1.1, you can have a single server listening on a single IP address that both DNS names resolve to.

In http 1.0, the context of name/address is implicit; in 1.1 it's explicitly given with Host:

L. 

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm