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=36741>. 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=36741 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Additional Comments From [EMAIL PROTECTED] 2005-09-22 01:52 ------- The idea behind this patch is to enable large headers being sent without using up excessive amounts of memory. For example, our application sometimes sets a lot of cookies. Instead of always preallocation memory and sometimes running out of buffer space when we cannot predict the cookie sizes correctly, we send everything through the same buffer. Also, the patch avoids a hard to diagnose exception. If you look around the web, you will see that other people ran into this condition as well. I have not seen any of them successfully identify the problem much less point at maxHttpHeaderSize as a workaround. As to calling this condition a "buffer overflow", it would be that had this code not been written in Java. http://forums.atlassian.com/thread.jspa?threadID=6121&tstart=75 http://mail-archive.objectweb.org/ops-users/2005-06/msg00109.html http://swforum.sun.com/jive/thread.jspa?threadID=50844&messageID=185391 -- 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]
