You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Alan M. Carroll (JIRA)" <ji...@apache.org> on 2011/08/31 00:44:10 UTC
[jira] [Commented] (TS-938) Our outgoing (request) Via: header
seems to always default to 127.0.0.1 as the IP identifier
[ https://issues.apache.org/jira/browse/TS-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094169#comment-13094169 ]
Alan M. Carroll commented on TS-938:
------------------------------------
According to the W3 spec (RFC2616 14.5)VIA headers should accumulate. We should check that
1) We accumulate them as required by the RFC.
2) We check the accumulated headers for a cycle.
> Our outgoing (request) Via: header seems to always default to 127.0.0.1 as the IP identifier
> --------------------------------------------------------------------------------------------
>
> Key: TS-938
> URL: https://issues.apache.org/jira/browse/TS-938
> Project: Traffic Server
> Issue Type: Bug
> Components: Network
> Affects Versions: 3.1.0
> Reporter: Leif Hedstrom
> Assignee: Alan M. Carroll
> Fix For: 3.1.1
>
>
> This can cause serious problems, because if the other end is also an ATS server, also defaulting to thinking it's on 127.0.0.1, will treat this as a loop, and send a 400 response.
> We ought to try to send something more intelligent as the hex-IP in the request Via: header. This is particularly problematic when ATS is used as a forward (or intercepting) proxy, and have outgoing Via: headers enabled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira