You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2012/11/02 04:54:12 UTC
[jira] [Commented] (TS-1558) use_client_addr breaks control over
upstream HTTP protocol version
[ https://issues.apache.org/jira/browse/TS-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489233#comment-13489233 ]
James Peach commented on TS-1558:
---------------------------------
a3fa8b6edfa4c5144f0716e8ef34f43b959cce94 Spell authorized consistently
> use_client_addr breaks control over upstream HTTP protocol version
> ------------------------------------------------------------------
>
> Key: TS-1558
> URL: https://issues.apache.org/jira/browse/TS-1558
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, HTTP
> Affects Versions: 3.3.3, 3.2.3
> Environment: Trunk running on CentOS 6.3, 64bit
> Reporter: Uri Shachar
> Priority: Critical
> Attachments: comment_typos.patch, use_client_version.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> If use_client_addr is turned on, we skip the hostdb lookup so we never know if the upstream has previously responded with an HTTP/1.1 response.
> This means that unless proxy.config.http.send_http11_requests is set to 1 we will always send HTTP/1.0 requests to upstream.
> I'll attach a patch that sets 'upstream server version = client request version' (which seems correct for a transparent interception scenario) -- an alternative implementation might be to modify the hostdb lookup flow to skip the actual DNS resolving and treat the client provided address as a DNS provided one -- Comments?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira