DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42625>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42625 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO ------- Additional Comments From [EMAIL PROTECTED] 2007-06-10 10:30 ------- You can do this with LimitRequestBody as long as no SSL renegotiation is needed for your request (e.g. due to SSLrequire used in a Directory / Location context) and even then you can use LimitRequestBody to limit what is being sent to your application (cgi script, whatever). If the request body is larger than what you set via LimitRequestBody but smaller than 128k, mod_ssl will consume the whole body and the error checking for LimitRequestBody will bail out later. If the request body is larger than 128k then mod_ssl will bail out regardless what is set for LimitRequestBody. As said this is only true in the case that a SSL renegotiation is needed. So the only limit that remains is that you cannot have request bodies larger than 128k if an SSL renegotiation is needed for your request and this is what is left from the original PR12355. Before the patch for PR12355 was applied no request body at all was possible with such renegotiated requests and now it can be up to 128k. Nevertheless many people complained afterwards that this size is not configurable and that 128k is not enough for their application. Please see PR12355 for further details. As far as I remember there were some proposals how to avoid renegotiation in such cases. To cut a long story short: If your request needs SSL renegotiation, then you are affected from what is left of PR12355 and if not it is highly likely that it is a misconfiguration on your side since the LimitRequestBody check in the HTTP_INPUT filter knows nothing about SSL. In this case please try using exactly the same configuration for SSL and non SSL and post both (SSL/non SSL) configurations here if it still does not work. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
