[
https://issues.apache.org/jira/browse/TS-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348947#comment-15348947
]
Kit Chan commented on TS-4587:
------------------------------
The escalate plugin does it in read response hook based on the status code of
the origin server response. I want to expand on that idea and do that based on
the server state from inside the TSRemapOSResponse function. And that's not
working
> Revisit TSRemapOSResponse
> -------------------------
>
> Key: TS-4587
> URL: https://issues.apache.org/jira/browse/TS-4587
> Project: Traffic Server
> Issue Type: Wish
> Components: Core, Plugins, Remap API, TS API
> Reporter: James Peach
>
> I looked at {{TSRemapOSResponse}}. This is a remap callback that is invoked
> synchronously in {{HttpTransact::handle_response_from_server()}} and gets
> passed a {{ServerState_t}} value.
> Note that there is no TSAPI analog for {{ServerState_t}}.
> The main difference between {{TSRemapOSResponse}} is that connection retries
> will be visible to {{TSRemapOSResponse}}. It's not that clear to me whether
> we have enough API for that to be interesting.
> This ticket is to investigate the utility of {{TSRemapOSResponse}}. If it is
> really helpful, then we should support it as a proper hook (global and
> transaction). If it's not then consider removing it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
