[
https://issues.apache.org/jira/browse/TS-4698?focusedWorklogId=25957&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25957
]
ASF GitHub Bot logged work on TS-4698:
--------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jul/16 15:49
Start Date: 23/Jul/16 15:49
Worklog Time Spent: 10m
Work Description: Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/822
Cool. Couple of things:
1) Please email dev@ with a short description for the API proposal. For
some details on the process of adding new APIs, see
https://cwiki.apache.org/confluence/display/TS/API+Review+Process.
2) Can you add some documentation as well? It doesn't have to be
particularly involved, but perhaps add it to TSHttpTxnIsInternal.en.rst? We
prefer to group related APIs together in a single man page type file.
3) I don't think we have any existing test harnesses or regression tests
for web sockets, but something to consider later.
Issue Time Tracking
-------------------
Worklog Id: (was: 25957)
Time Spent: 0.5h (was: 20m)
> Add an API call to detect websocket connections
> -----------------------------------------------
>
> Key: TS-4698
> URL: https://issues.apache.org/jira/browse/TS-4698
> Project: Traffic Server
> Issue Type: Improvement
> Components: TS API
> Affects Versions: 7.0.0
> Reporter: Oliver Goodman
> Assignee: Oliver Goodman
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It is possible for TS to terminate websocket connections using a server
> intercept plugin but in order to do so the plugin needs a reliable way to
> identify such connections. This information is known and used internally but
> not AFAICT yet exposed via the TS API. It is here proposed that a simple call
> be added to return this information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
