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=5322>. 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=5322 HttpResonseBase class sends headers with multiple field-values in a non HTTP compliant fashion. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2001-12-09 20:56 ------- Per Section 4.2 of the HTTP/1.1 specification (RFC 2616), it is only legal to combine multiple values for the same header name *if* the semantics doesn't change. In other words, you have to ensure that a comma character is not included in any of the values. On the other hand, it is *always* legal to have the multiple values for the same header name to be provided on separate HTTP header lines. Robust client applications need to be ready to deal with either approach. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
