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 (JIRA)" <ji...@apache.org> on 2011/08/31 00:32:11 UTC
[jira] [Created] (TS-938) Our outgoing (request) Via: header seems
to always default to 127.0.0.1 as the IP identifier
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
[jira] [Commented] (TS-938) Our outgoing (request) Via: header
seems to always default to 127.0.0.1 as the IP identifier
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (TS-938) Our outgoing (request) Via: header
seems to always default to 127.0.0.1 as the IP identifier
Posted by "Alan M. Carroll (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124632#comment-13124632 ]
Alan M. Carroll commented on TS-938:
------------------------------------
For the fix, the address used is (in order of preference)
1) The outgoing_ip_to_bind
2) The incoming_ip_to_bind
3) An address selected from an interface.
If an address is selected automatically, global addresses are preferred, then multicast, non-routable, and finally loopback.
Use the per-transaction outbound IP address was considered but this makes the cycle checking (the entire point of this work) problematic as it is then unclear what to check against, the original transaction (and its associated outbound IP address) unable to be accurately determined.
> 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.
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
[jira] [Resolved] (TS-938) Our outgoing (request) Via: header seems
to always default to 127.0.0.1 as the IP identifier
Posted by "Alan M. Carroll (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan M. Carroll resolved TS-938.
--------------------------------
Resolution: Fixed
> 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.
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