DO NOT REPLY [Bug 39243] - Can't post files larger than 128k onto ssl client cert secured site

[bu...@apache.org]

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=39243>.
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=39243


p.c.c.wagemans@kpn.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |




------- Additional Comments From p.c.c.wagemans@kpn.com  2006-06-28 15:15 -------
There may be good functional reasons for POSTs larger than 128k and to
require client certificates only for access to certain URLs. And
asking for an optional client certificate at SSL connect bothers users
of other URLs with unnecessary prompts for client certificates that
they may not have and don't need (depending on the browser that they
use).

For us the hard-coded limit is still a problem.

> It would require to introduce disk buffering of the POST request
> body.

This is not clear to me. Where is the hard-coded limit of 128k coming
from?

Could the code not look at the value of the directive LimitRequestBody
and if it is set allow SSL request bodies of that size?

-- 
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org