[jira] Closed: (TS-532) possible misbehavior with HEAD request before GET

["Zhao Yongming (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhao Yongming closed TS-532.
----------------------------

    Resolution: Invalid

This is invalid, I will post a project on create options to get loop detection more configurable later.

what we need to do is not just IP, but also hostanme(cluster name) etc

> possible misbehavior with HEAD request before GET
> -------------------------------------------------
>
>                 Key: TS-532
>                 URL: https://issues.apache.org/jira/browse/TS-532
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP
>         Environment: we have many haproxy before the TS server, do L7 hashing for all request
>            Reporter: Zhao Yongming
>            Priority: Trivial
>             Fix For: 2.1.6
>
>         Attachments: 35425.cap, 434.cap, 8092.cap
>
>
> sometimes there is many HEAD request flood in, looks like cache in loop, but TS does not identify it as a loop.
> as the HEAD request will all pass to OS, that will make OS unable to response for sometime? get 1-5k connections, make TS get throttling.
> here is some tcpdum cap file
> why I suspect HEAD request, is when I ban all HEAD request use quick filter mask, the connection rush is gone.
> but this could be other problem indeed. just open this bug for logging.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.