Worked like a charm. I had APREQ_ReadLimit in a vhost ... Once moving it out
of the vhost I can now upload bigger files. Should have used the mailing list
before making an indentation in the brick wall with my forehead.
Many thanks!
Tim Hibbard
On 1/25/11 1:31 PM, "Joe Schaefer" wrote:
It
1) You may lower the limit, not raise it. If you are trying to raise
it, you will get "Conflicting information".
2) Your server config trumps your virtual-host config. If you have not
set APREQ2_ReadLimit outside of your VirtualHost, then it is set for you
(64M).
Personally, I do this:
A)
It's a bug in the merge code for mod_apreq2. Basically
you have to set APREQ_ReadLimit to its max value
in the main server's context (not in a vhost or Location
or Directory config).
Otherwise use the code in apreq's trunk.
>
>From: "Hibbard, Timothy"
>To: "modperl@perl.apache.org"
>Sent: Tu
