You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Eric Balsa (JIRA)" <ji...@apache.org> on 2010/11/19 18:46:14 UTC
[jira] Assigned: (TS-529) Re-order pre_remap hook
[ https://issues.apache.org/jira/browse/TS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Balsa reassigned TS-529:
-----------------------------
Assignee: Eric Balsa
> Re-order pre_remap hook
> -----------------------
>
> Key: TS-529
> URL: https://issues.apache.org/jira/browse/TS-529
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Affects Versions: 2.1.3
> Reporter: Eric Balsa
> Assignee: Eric Balsa
> Fix For: 2.1.5
>
>
> Currently, the ordering of API hooks is:
> txn_start -> [receive headers from client] -> pre_remap -> remap -> read_request -> os_dns_lookup
> This should be ordered differently:
> txn_start -> [receive headers from client] -> read_request -> pre_remap -> remap -> post_remap -> os_dns_lookup
> This would involve adding a post_remap API hook and re-arranged the SM ordering of hooks to more closely match what you would expect.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.