httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 39243] - Can't post files larger than 128k onto ssl client cert secured site
Date Fri, 14 Jul 2006 07:33:21 GMT
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





------- Additional Comments From p.c.c.wagemans@kpn.com  2006-07-14 07:33 -------
> But you should really design your site to ensure that the first
> request to a client-cert-protected area is not a POST request with a
> large body; make it a GET or something.

Not really an option with SOAP.

> I have to believe the "one size limit fits all" approach will not
> work for all the existing applications in the world.

Agreed.

> However, shouldn't we add a SSLMaxIOBuffer directive instead of
> hardcoding the value at build time?

That is a good way to remove the hard-coded limit. But is there a
reason why one could not use the existing directive LimitRequestBody,
as suggested above? It can be set for the client cert protected area
and then defines the size of requests that should be handled, thus the
amount that should be allowed to be buffered.

-- 
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


Mime
View raw message