[
https://issues.apache.org/jira/browse/TS-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933002#action_12933002
]
Zhao Yongming commented on TS-532:
----------------------------------
seems the OPTIONS request can kill me too.
any common? they just can not cache by TS at all.
> 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
> 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.
