[
https://issues.apache.org/jira/browse/TS-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157575#comment-14157575
]
Thomas Jackson commented on TS-3106:
------------------------------------
Been digging a little bit to see how other proxies handle this case (redirect
or something similar when a body is involved). I dug through the haproxy source
and what they do is check if the request can have a body-- and if so they will
close the connection, otherwise the connection is kept alive. This should be
doable in ATS as it already enforces that certain types of requests cannot have
bodies (such as HEAD requests, you get a 403).
References:
- https://github.com/haproxy/haproxy/blob/master/src/proto_http.c#L3943
- https://github.com/haproxy/haproxy/blob/master/src/proto_http.c#L6042
> ATS error responses do not flush request body
> ---------------------------------------------
>
> Key: TS-3106
> URL: https://issues.apache.org/jira/browse/TS-3106
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Thomas Jackson
> Assignee: Brian Geffon
> Fix For: 5.2.0
>
>
> If you send a request to ATS which causes an error page (no remap, blocked
> HTTP method, etc.) with a body, the following request will get a 403
> response. This is due to ATS not flushing the request body of the first
> (failed) request. If you look in the logs for the second request you will see
> the URL as "POSBODY GET /" (or something similar). I can easily reproduce
> this on ATS 5.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
