You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by clearswift <gi...@git.apache.org> on 2016/11/29 14:40:36 UTC

[GitHub] trafficserver issue #1237: Slowloris vulnerability

GitHub user clearswift opened an issue:

    https://github.com/apache/trafficserver/issues/1237

    Slowloris vulnerability

    Traffic server is "likely vulnerable" to slowloris (see https://nmap.org/nsedoc/scripts/http-slowloris-check.html) in both reverse and forward proxy mode.
    
    Has anyone investigated this yet? Is there any plan to do anything about it? I appreciate the nature of the vulnerability means fully fixing it is likely impossible, I'm just trying to find out if there's an official position on the issue.
    
    Thanks.

----

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] trafficserver issue #1237: Slowloris vulnerability

Posted by zwoop <gi...@git.apache.org>.
Github user zwoop commented on the issue:

    https://github.com/apache/trafficserver/issues/1237
  
    I think think you can set a timeout (proxy.config.http.transaction_active_timeout_in) which doesn't care if data is being sent or not (it's a "hard" timeout on an active connection).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---