https://bz.apache.org/bugzilla/show_bug.cgi?id=58464

Gonzalo <yogonza...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WONTFIX                     |---
             Status|RESOLVED                    |REOPENED

--- Comment #5 from Gonzalo <yogonza...@gmail.com> ---
Hello, 

Marks said:
"Unless there is something in one of the specifications that Tomcat implements
that mandates header case is preserved (unlikely given that the HTTP spec
states header names are case insensitive) this is going to get resolved as
WONTFIX."

This issue must be reopened because the HTTP protocol is not be respected by
Tomcat. Duplicated headers are not a problem as well, but that behavior is
breaking the protocol when header Transfer-Encoding is duplicated with the
value "chunked". Topic related at
https://tools.ietf.org/html/rfc7230#section-3.3.1

The important:
   A recipient MUST be able to parse the chunked transfer coding
   (Section 4.1) because it plays a crucial role in framing messages
   when the payload body size is not known in advance.  A sender MUST
   NOT apply chunked more than once to a message body (i.e., chunking an
   already chunked message is not allowed).  If any transfer coding
   other than chunked is applied to a request payload body, the sender
   MUST apply chunked as the final transfer coding to ensure that the
   message is properly framed.  If any transfer coding other than
   chunked is applied to a response payload body, the sender MUST either
   apply chunked as the final transfer coding or terminate the message
   by closing the connection.

That is a big problem when you are at Cloud environments using Envoy proxy with
Istio, more info about it here:
https://discuss.istio.io/t/unsupported-transfer-encoding-error-in-istio-proxy/6021/8
 

I think this must be fixed, at my case my team will change all Tomcat servers
to Undertow just to workaround this issue (more than 1500 Tomcat servers)

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to