[
https://issues.apache.org/jira/browse/TS-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353828#comment-15353828
]
Kit Chan commented on TS-4587:
------------------------------
So I end up getting TSHttpTxnRedirectUrlSet to work with TSRemapOSResponse
As long as I have a handler with the send response hook, it will work.
So now, in my setup, I enhance escalate plugin to have a function for
TSRemapOSResponse(). Inside I checked the server state and if it is not alive,
I will set use TSHttpTxnRedirectUrlSet() to set a redirect url. And thus I
allow the transaction to try out a different destination in situation such as a
DNS error or timeout.
> 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
> Fix For: 7.0.0
>
>
> 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)
