Sorry slight clarification here after rereading httpd source:
If you send anything other than that "Continue: 100" interim
response to the client, httpd will NOT attempt to read the
body, considering it empty. But even if you do send the
"Continue: 100", httpd will NOT block the response from bei
Joe Schaefer wrote:
I don't think people groked my point very well. When you POST
via HTTP/1.1, httpd will send a "Continue: 100" header before it
starts doing blocking reads on the client socket (any attempts to
read from the client will trigger this behavior). If you really
want to interrupt a
I don't think people groked my point very well. When you POST
via HTTP/1.1, httpd will send a "Continue: 100" header before it
starts doing blocking reads on the client socket (any attempts to
read from the client will trigger this behavior). If you really
want to interrupt an upload, the time to
Le mercredi 08 février 2012 à 05:53 -0800, mike cardeiro a écrit :
> This is a fantastic list!
Agreed.
On the same note : I was recently presenting the legal case management
app in my sig to an institutional client in the south of France, and the
IT guy said that it had a 'fantastic architecture
> From: Torsten Förtsch
>
> Best would be if you could make an educated guess based on the Content-Length
> request header if the uploaded file will exceed the limit. Most clients send
> an "Expect: 100-continue" header and thus give the server a chance to
> decline
> the request *before* the
Torsten Förtsch wrote:
On Wednesday, 08 February 2012 10:14:35 André Warnier wrote:
As far as I know, LimitRequestBody is an absolute POST size limit set once
and for all in the server config, and valid for all POSTs (and PUTs) after
server restart.
If you look at the docs you'll find that Li
On Wednesday, 08 February 2012 10:14:35 André Warnier wrote:
> As far as I know, LimitRequestBody is an absolute POST size limit set once
> and for all in the server config, and valid for all POSTs (and PUTs) after
> server restart.
If you look at the docs you'll find that LimitRequestBody is val
You probably don't want to do this with a hook if you can
avoid it. The reason is that once httpd sends the 100 Continue
it will read the entire upload, even after CGI.pm or apreq
has stopped parsing it.
- Original Message -
> From: André Warnier
> To: mod_perl list
> Cc:
> Sent: Wed
This refers to and follows another thread originally entitled "mod perl installed but not
running", started by Mike Cardeiro.
It seemed better to start a new thread with a subject more to the point of this
issue.
Perrin Harkins wrote:
> On Tue, Feb 7, 2012 at 7:26 PM, André Warnier wrote:
>>
