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/03/11 01:51:27 UTC
[jira] Created: (TS-237) catch-all remap rule ("map / ....")
stopped working after lookup optimizations
catch-all remap rule ("map / ....") stopped working after lookup optimizations
-------------------------------------------------------------------------------
Key: TS-237
URL: https://issues.apache.org/jira/browse/TS-237
Project: Traffic Server
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0a
Reporter: Manjesh Nilange
Assignee: Manjesh Nilange
Priority: Minor
Fix For: 2.0.0
A "catch-all" remap rule like:
map / http://example.com
has stopped working after the changes checked in for TS-87 were checked in. This is because the logic of returning the first available rule for an empty host was cut out of the code. Also, the UrlMappingPathIndex class should use scheme and not url_type as scheme has higher resolution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TS-237) catch-all remap rule ("map / ....")
stopped working after lookup optimizations
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom resolved TS-237.
------------------------------
Resolution: Fixed
> catch-all remap rule ("map / ....") stopped working after lookup optimizations
> -------------------------------------------------------------------------------
>
> Key: TS-237
> URL: https://issues.apache.org/jira/browse/TS-237
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0a
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: catchall-remap.patch
>
>
> A "catch-all" remap rule like:
> map / http://example.com
> has stopped working after the changes checked in for TS-87 were checked in. This is because the logic of returning the first available rule for an empty host was cut out of the code. Also, the UrlMappingPathIndex class should use scheme and not url_type as scheme has higher resolution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TS-237) catch-all remap rule ("map / ....")
stopped working after lookup optimizations
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjesh Nilange updated TS-237:
-------------------------------
Attachment: catchall-remap.patch
Proposed change.
> catch-all remap rule ("map / ....") stopped working after lookup optimizations
> -------------------------------------------------------------------------------
>
> Key: TS-237
> URL: https://issues.apache.org/jira/browse/TS-237
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0a
> Reporter: Manjesh Nilange
> Assignee: Manjesh Nilange
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: catchall-remap.patch
>
>
> A "catch-all" remap rule like:
> map / http://example.com
> has stopped working after the changes checked in for TS-87 were checked in. This is because the logic of returning the first available rule for an empty host was cut out of the code. Also, the UrlMappingPathIndex class should use scheme and not url_type as scheme has higher resolution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TS-237) catch-all remap rule ("map / ....") stopped
working after lookup optimizations
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom closed TS-237.
----------------------------
> catch-all remap rule ("map / ....") stopped working after lookup optimizations
> -------------------------------------------------------------------------------
>
> Key: TS-237
> URL: https://issues.apache.org/jira/browse/TS-237
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0a
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: catchall-remap.patch
>
>
> A "catch-all" remap rule like:
> map / http://example.com
> has stopped working after the changes checked in for TS-87 were checked in. This is because the logic of returning the first available rule for an empty host was cut out of the code. Also, the UrlMappingPathIndex class should use scheme and not url_type as scheme has higher resolution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TS-237) catch-all remap rule ("map / ....")
stopped working after lookup optimizations
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjesh Nilange reassigned TS-237:
----------------------------------
Assignee: Leif Hedstrom (was: Manjesh Nilange)
Leif, review please.
> catch-all remap rule ("map / ....") stopped working after lookup optimizations
> -------------------------------------------------------------------------------
>
> Key: TS-237
> URL: https://issues.apache.org/jira/browse/TS-237
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0a
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: catchall-remap.patch
>
>
> A "catch-all" remap rule like:
> map / http://example.com
> has stopped working after the changes checked in for TS-87 were checked in. This is because the logic of returning the first available rule for an empty host was cut out of the code. Also, the UrlMappingPathIndex class should use scheme and not url_type as scheme has higher resolution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.