On Wed, Jun 15, 2011 at 8:40 PM, Eric Balsa <[email protected]> wrote:
> Subbu, we blast hop-by-hop headers (HTIF_HOPBYHOP / > MIME_FLAGS_HOPBYHOP) from the origin request. This happens in > HttpTransactHeaders::copy_header_fields so your origin will never see > those fields. > > Upgrade: & Connection: are defined as hop-by-hop header fields in the > TS source. Whether that is correct, i defer to the HTTP experts ;) > mnot? > > --Eric > > On Wed, Jun 15, 2011 at 5:38 PM, Eric Balsa <[email protected]> wrote: > > Subbu, we blast hop-by-hop headers (HTIF_HOPBYHOP / > > MIME_FLAGS_HOPBYHOP) from the origin request. This happens in > > HttpTransactHeaders::copy_header_fields so your origin will never see > > those fields. > > > > Upgrade: & Connection: are defined as hop-by-hop header fields in the > > TS source. Whether that is correct, i defer to the HTTP experts ;) > > mnot? > That is right. Below are all the headers that the RFC defines as hop-by-hop headers, these can't be forwarded to origin servers as per the spec. Sridhar The following HTTP/1.1 headers are hop-by-hop headers: - Connection - Keep-Alive - Proxy-Authenticate - Proxy-Authorization - TE - Trailers - Transfer-Encoding - Upgrade
