[
https://issues.apache.org/jira/browse/TS-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429561#comment-15429561
]
William Bardwell commented on TS-3341:
--------------------------------------
I have some code, it seems to occasionally claim that things were aborted that
don't look like they were...when I get some slack I would still like to deal
with this.
> Add plugin APIs about server transaction status
> -----------------------------------------------
>
> Key: TS-3341
> URL: https://issues.apache.org/jira/browse/TS-3341
> Project: Traffic Server
> Issue Type: Improvement
> Components: TS API
> Reporter: William Bardwell
> Assignee: William Bardwell
> Fix For: sometime
>
>
> {code}
> // Indicates if the connection to the client was aborted,
> // will not be true if the client closed cleanly at the end
> // of the transaction.
> int
> TSHttpTxnServerTransactionClientAbortGet(TSHttpTxn txnp)
> {
> sdk_assert(sdk_sanity_check_txn(txnp) == TS_SUCCESS);
> HttpTransact::State *s = &(((HttpSM *) txnp)->t_state);
> return (s->client_info.abort == HttpTransact::ABORTED);
> }
> {code}
> {code}
> // Indicates if the transaction with the origin server is complete.
> // Will be true if the connection to the origin never started or
> // failed, as well as if it finished successfully. If this is checked
> // to early or for a cache hit, it will return true.
> int
> TSHttpTxnServerTransactionCompleteGet(TSHttpTxn txnp)
> {
> sdk_assert(sdk_sanity_check_txn(txnp) == TS_SUCCESS);
> HttpTransact::State *s = &(((HttpSM *) txnp)->t_state);
> return ((TSServerState)s->current.state != TS_SRVSTATE_CONNECTION_ALIVE) ||
> (s->current.server ? (s->current.server->state ==
> HttpTransact::TRANSACTION_COMPLETE):false);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
