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 Sun, 23 Jul 2006 20:04:57 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 wrowe@apache.org  2006-07-23 20:04 -------
We can allow to to configure this to be larger at a serious cost to how
many requests you can process.

The obvious answer for an 'upload' style operation is to ensure they never
hit your upload page without going through a simpler front page which first
enforces the renegotation.  This can be your upload form page.

Once the session is SSLClientVerify'ed it won't renegotate -again- so this
problem won't occur.

No matter what -we- do, if you design your huge-post page such that it won't
cause renegotiation on large posts, your server will always have less stress.
And that's a good thing IMHO.  2GB set asides are absurd, but pushing up a
2GB iso image isn't inconcievable.


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