You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by "Manjesh Nilange (JIRA)" <ji...@apache.org> on 2010/02/16 18:45:28 UTC
[jira] Created: (TS-184) Host header/cache lookup entry doesn't
match remap.config perfectly
Host header/cache lookup entry doesn't match remap.config perfectly
-------------------------------------------------------------------
Key: TS-184
URL: https://issues.apache.org/jira/browse/TS-184
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Manjesh Nilange
Assignee: Manjesh Nilange
Priority: Minor
Fix For: 2.0.0a
Attachments: port-80.patch
If I had this in my remap.config
map http://a.com http://b.com:80
The Host header and the cache key constructed by TS had the ":80" in the string based on the incoming request. If the incoming request explicitly specified ":80", then the cache key/host header would also have it. We should construct the cache key/host header exactly as specified in the remap.config
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TS-184) Host header/cache lookup entry doesn't
match remap.config perfectly
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom resolved TS-184.
------------------------------
Resolution: Fixed
> Host header/cache lookup entry doesn't match remap.config perfectly
> -------------------------------------------------------------------
>
> Key: TS-184
> URL: https://issues.apache.org/jira/browse/TS-184
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 2.0.0a
>
> Attachments: port-80.patch, port-80.patch
>
>
> If I had this in my remap.config
> map http://a.com http://b.com:80
> The Host header and the cache key constructed by TS had the ":80" in the string based on the incoming request. If the incoming request explicitly specified ":80", then the cache key/host header would also have it. We should construct the cache key/host header exactly as specified in the remap.config
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TS-184) Host header/cache lookup entry doesn't
match remap.config perfectly
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjesh Nilange updated TS-184:
-------------------------------
Attachment: port-80.patch
Patch on top of TS-87 changes.
> Host header/cache lookup entry doesn't match remap.config perfectly
> -------------------------------------------------------------------
>
> Key: TS-184
> URL: https://issues.apache.org/jira/browse/TS-184
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 2.0.0a
>
> Attachments: port-80.patch, port-80.patch
>
>
> If I had this in my remap.config
> map http://a.com http://b.com:80
> The Host header and the cache key constructed by TS had the ":80" in the string based on the incoming request. If the incoming request explicitly specified ":80", then the cache key/host header would also have it. We should construct the cache key/host header exactly as specified in the remap.config
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TS-184) Host header/cache lookup entry doesn't
match remap.config perfectly
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834559#action_12834559 ]
Leif Hedstrom commented on TS-184:
----------------------------------
Even though it'd be pretty easy to "fix" this patch, it'd be great if you could prepare an updated diff that's based on trunk with TS-87 applied.
Thanks!
> Host header/cache lookup entry doesn't match remap.config perfectly
> -------------------------------------------------------------------
>
> Key: TS-184
> URL: https://issues.apache.org/jira/browse/TS-184
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 2.0.0a
>
> Attachments: port-80.patch
>
>
> If I had this in my remap.config
> map http://a.com http://b.com:80
> The Host header and the cache key constructed by TS had the ":80" in the string based on the incoming request. If the incoming request explicitly specified ":80", then the cache key/host header would also have it. We should construct the cache key/host header exactly as specified in the remap.config
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TS-184) Host header/cache lookup entry doesn't
match remap.config perfectly
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjesh Nilange reassigned TS-184:
----------------------------------
Assignee: Leif Hedstrom (was: Manjesh Nilange)
Leif, please review. Thanks!
> Host header/cache lookup entry doesn't match remap.config perfectly
> -------------------------------------------------------------------
>
> Key: TS-184
> URL: https://issues.apache.org/jira/browse/TS-184
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 2.0.0a
>
> Attachments: port-80.patch
>
>
> If I had this in my remap.config
> map http://a.com http://b.com:80
> The Host header and the cache key constructed by TS had the ":80" in the string based on the incoming request. If the incoming request explicitly specified ":80", then the cache key/host header would also have it. We should construct the cache key/host header exactly as specified in the remap.config
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TS-184) Host header/cache lookup entry doesn't
match remap.config perfectly
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjesh Nilange updated TS-184:
-------------------------------
Attachment: port-80.patch
Patch to set the port to match exactly what's specified in remap.config
> Host header/cache lookup entry doesn't match remap.config perfectly
> -------------------------------------------------------------------
>
> Key: TS-184
> URL: https://issues.apache.org/jira/browse/TS-184
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Manjesh Nilange
> Assignee: Manjesh Nilange
> Priority: Minor
> Fix For: 2.0.0a
>
> Attachments: port-80.patch
>
>
> If I had this in my remap.config
> map http://a.com http://b.com:80
> The Host header and the cache key constructed by TS had the ":80" in the string based on the incoming request. If the incoming request explicitly specified ":80", then the cache key/host header would also have it. We should construct the cache key/host header exactly as specified in the remap.config
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.