Re: [squid-users] "_" (underline) in website names

----- Original Message -----
From: "LA Walsh" <law@sgi.com>
To: "Stefan Berg" <stefan.berg@ausystem.com>
Cc: <squid-users@squid-cache.org>
Sent: Saturday, May 19, 2001 12:51 AM
Subject: Re: [squid-users] "_" (underline) in website names

> Stefan Berg wrote:
>
> > Hi,
> >
> > check out the RFC 2396 - it states that the underscore isn't allowed
as part
> > of hostname in an URL. So squid is simply being standard compliant.
>
> ---
> Squid is not just being standard compliant -- it is being standard
enforcing.
> There's a difference.
>

Not for RFC 2616. "a proxy MUST implement both the client and server
requirements." Squid is not permitted to forward requests that do not
meet the requirements of the specification. Thus squid is not allowed to
forward requests with "_" in the hostname.

Rob

"Fielding, et al. Standards Track [Page
9]

RFC 2616 HTTP/1.1 June 1999

   origin server
      The server on which a given resource resides or is to be created.

   proxy
      An intermediary program which acts as both a server and a client
      for the purpose of making requests on behalf of other clients.
      Requests are serviced internally or by passing them on, with
      possible translation, to other servers. A proxy MUST implement
      both the client and server requirements of this specification. A
      "transparent proxy" is a proxy that does not modify the request or
      response beyond what is required for proxy authentication and
      identification. A "non-transparent proxy" is a proxy that modifies
      the request or response in order to provide some added service to
      the user agent, such as group annotation services, media type
      transformation, protocol reduction, or anonymity filtering. Except
      where either transparent or non-transparent behavior is explicitly
      stated, the HTTP proxy requirements apply to both types of
      proxies.
"
Received on Fri May 18 2001 - 20:41:55 MDT