> Under what criteria, missing Content-Length? You can probably set
that
> up more directly w/ e.g. mod_rewrite.
I'm not sure whether I understand that right.
Does the question refer to which exact case the 100-Continue status
shouldn't be sent?
--That would be in case my cgi-bin determines tha
On Fri, Dec 6, 2013 at 9:24 AM, Andreas Frisch
wrote:
>> > or keep apache from sending the 100 - continue statement right away?
>
>>
>
>> What would it do instead?
>
>>
>
> Ιf it didn't send the continue at all, then at least the client side could
> detect a timeout and interrupt the upload itself
> > or keep apache from sending the 100 - continue
statement right away?
>
> What would it do instead?
>
Ιf it didn't send the continue at all, then at least the
client side could detect a timeout and interrupt the
upload itself rather than just keep sending data
forever that apache has to dis
> or keep apache from sending the 100 - continue statement right away?
What would it do instead?
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
Hi, I have a peer that does an HTTP PUT using curl to my apache 2.2.25
running a cgi written in c.
Under certain conditions, the cgi-bin terminates with an HTTP error
status, like 400. This will keep a file from being uploaded as expected.
However, when the content-length of the upload is unspeci
