DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24012>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24012 Ability to ignore (reject) cookies altogether ------- Additional Comments From [EMAIL PROTECTED] 2003-10-23 06:22 ------- I wonder whether cookie policy is the right place to address this particular issue. I'm using the HTTP Client as an implementation of RFC 2616 (HTTP 1.1), and cookies are specified in RFC 2965. I'd prefer a way to switch off cookie parsing altogether, like I can switch off automatic authentication or redirect handling. Preferably with the cookie parsing logic exposed to the programmer, for cases when the application decides to parse some or all cookies anyway. Currently, I'm using a derived HttpState implementation that overrides all setters to no-ops. The primary reason for this is that my HttpState object becomes read-only and the same object can be used by various threads simultaneously without interferences. But I guess that's 3.0 talk. For 2.1, the 'reject-all-damn-cookies' policy sounds like an appropriate solution that can be implemented with little effort. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
