[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-httpd-users
Subject:    [users@httpd] Re: How to upload Files larger than 2GB
From:       Martin Knoblauch <knobisoft () googlemail ! com ! INVALID>
Date:       2020-08-19 14:29:18
Message-ID: CAJtcoLaKa=DZxEqqygAf99AHAJKnLcZ1+W=gfmbgafwF76wQFQ () mail ! gmail ! com
[Download RAW message or body]

Hi Mark,

 thanks for the reply. The mentioning of "Chunked" helped me solve the
problem. Our perl based REST client clearly tried to send the file as one
buffer. Fortunately changing that was on line of code.



> >
> > 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.
>
>
Thanks for clarifying that.


> 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?
>
>
 Apparently with content-length. Changing to "chunked" solved it.

Thanks again
Martin
-- 
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de

[Attachment #3 (text/html)]

<div dir="ltr"><div>Hi Mark,</div><div><br></div><div>  thanks for the reply. The \
mentioning of &quot;Chunked&quot; helped me solve the problem. Our perl based REST \
client clearly tried to send the file as one buffer. Fortunately changing that was on \
line of code.</div><div><br></div><br><div class="gmail_quote"><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><br> &gt; <br>
&gt; Then looking at the Tomcat configuration. The HTTP connector (working)<br>
&gt; looks like this:<br>
&gt; <br>
&gt;        &lt;Connector port=&quot;9695&quot; protocol=&quot;HTTP/1.1&quot;<br>
&gt;                        connectionTimeout=&quot;20000&quot;<br>
&gt;                        maxPostSize=&quot;209715200&quot;<br>
&gt;                        redirectPort=&quot;8443&quot; /&gt;<br>
&gt; <br>
&gt; Which makes me wonder why it works. It should bail out at 200 MB.<br>
<br>
That limit only applies to the automated processing of request bodies as<br>
per section 3.1.1 of the Servlet 4.0 specification.<br>
<br>
If the application (or a library it uses) reads the request body<br>
directly, there is no limit. The application is meant to provide<br>
whatever limits it considers appropriate.<br>
<br></blockquote><div><br></div><div>Thanks for clarifying that.</div><div>  \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex"> I wonder if httpd/mod_jk is trying cache \
the entire request body before<br> forwarding. How is the request sent? With \
chunked-encoding or with a<br> content-length? Does switching to the other one \
help?<br> <br clear="all"></blockquote><div><br></div><div>  Apparently with \
content-length. Changing to &quot;chunked&quot; solved \
it.</div><div><br></div><div>Thanks again<br></div></div>Martin<br><div>-- <br><div \
dir="ltr" class="gmail_signature"><div \
dir="ltr">------------------------------------------------------<br>Martin \
Knoblauch<br>email: k n o b i AT knobisoft DOT de<br>www:   <a \
href="http://www.knobisoft.de" \
target="_blank">http://www.knobisoft.de</a><br><br></div></div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]