You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (Updated) (JIRA)" <ji...@apache.org> on 2011/10/05 00:28:34 UTC
[jira] [Updated] (TS-467) Proxy shold not forward request headers
that matches a Connection token
[ https://issues.apache.org/jira/browse/TS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-467:
-----------------------------
Fix Version/s: (was: 3.1.1)
3.3.0
> Proxy shold not forward request headers that matches a Connection token
> -----------------------------------------------------------------------
>
> Key: TS-467
> URL: https://issues.apache.org/jira/browse/TS-467
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Leif Hedstrom
> Fix For: 3.3.0
>
>
> If a client sends a request like
> X-foobar: fum
> Connection: ,,X-foobar,,
> the proxy (Traffic Server) MUST remove the header X-foobar before forwarding the request. From the RFC:
> HTTP/1.1 proxies MUST parse the Connection header field before a
> message is forwarded and, for each connection-token in this field,
> remove any header field(s) from the message with the same name as the
> connection-token.
> and
> A system receiving an HTTP/1.0 (or lower-version) message that
> includes a Connection header MUST, for each connection-token in this
> field, remove and ignore any header field(s) from the message with
> the same name as the connection-token.
> (Originally discovered with Coadvisor).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira