[
https://issues.apache.org/jira/browse/TS-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Sime resolved TS-4675.
--------------------------
Resolution: Fixed
Reordered the individual hooks in the documentation to reflect the order in
which they occur during an event's life. Fixed the descriptions that were noted.
> header_rewrite hook descriptions are wrong
> ------------------------------------------
>
> Key: TS-4675
> URL: https://issues.apache.org/jira/browse/TS-4675
> Project: Traffic Server
> Issue Type: Bug
> Components: Documentation
> Reporter: Miles Libbey
> Assignee: Jon Sime
> Fix For: Docs
>
>
> - REMAP_PSEUDO_HOOK is not similar to READ_RESPONSE_HDR_HOOK.
> - Think that READ_RESPONSE_HDR_HOOK and READ_REQUEST_PRE_REMAP_HOOK are
> aliases to each other.
> ( #define TS_HTTP_READ_REQUEST_PRE_REMAP_HOOK TS_HTTP_PRE_REMAP_HOOK /*
> backwards compat */)
> - Should note that READ_REQUEST_PRE_REMAP_HOOK/READ_REQUEST_HDR_HOOK can not
> be applied to remap rules. Just global rules.
> - REMAP_PSEUDO_HOOK doesn't show in
> https://docs.trafficserver.apache.org/en/latest/developer-guide/plugins/hooks-and-transactions/index.en.html#http-transaction-state-diagram
> , so don't know when it actually fires.
> - We should present the hooks in order of their firing. Eg,
> READ_RESPONSE_HDR_HOOK should be after pre_remap...
> - Seems like we should have a diagram similar to
> https://docs.trafficserver.apache.org/en/latest/developer-guide/plugins/hooks-and-transactions/index.en.html#http-transaction-state-diagram
> on the page. (With the header_rewrite names, and simplified -- don't need
> all the gory oval detail.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
