You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/23 11:48:20 UTC

[jira] [Work logged] (TS-4698) Add an API call to detect websocket connections

     [ https://issues.apache.org/jira/browse/TS-4698?focusedWorklogId=25942&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25942 ]

ASF GitHub Bot logged work on TS-4698:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Jul/16 11:47
            Start Date: 23/Jul/16 11:47
    Worklog Time Spent: 10m 
      Work Description: Github user ogoodman commented on the issue:

    https://github.com/apache/trafficserver/pull/624
  
    I'm going to close this particular PR now as it has become messy, doesn't reference any JIRA issue, and needs to be split into a PR on the TS API followed by one which adds the example to the C++ API.
    JIRA issues TS-4698 and TS-4699 have been created for the two improvements.


Issue Time Tracking
-------------------

            Worklog Id:     (was: 25942)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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
>            Reporter: Oliver Goodman
>          Time Spent: 10m
>  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)