>
> Then looking at the Tomcat configuration. The HTTP connector (working)
> looks like this:
>
> <Connector port="9695" protocol="HTTP/1.1"
> connectionTimeout="20000"
> maxPostSize="209715200"
> redirectPort="8443" />
>
> Which makes me wonder why it works. It should bail out at 200 MB.
That limit only applies to the automated processing of request bodies as
per section 3.1.1 of the Servlet 4.0 specification.
If the application (or a library it uses) reads the request body
directly, there is no limit. The application is meant to provide
whatever limits it considers appropriate.
I wonder if httpd/mod_jk is trying cache the entire request body before
forwarding. How is the request sent? With chunked-encoding or with a
content-length? Does switching to the other one help?