[wp-trac] [WordPress Trac] #13513: Processing HTTP Headers violates RFC 2616

WordPress Trac wp-trac at lists.automattic.com
Tue Mar 22 07:05:18 UTC 2011

#13513: Processing HTTP Headers violates RFC 2616
 Reporter:  hakre                        |       Owner:  dd32
     Type:  defect (bug)                 |      Status:  accepted
 Priority:  normal                       |   Milestone:  Future Release
Component:  HTTP                         |     Version:  3.0
 Severity:  normal                       |  Resolution:
 Keywords:  has-patch close 2nd-opinion  |
Changes (by dd32):

 * keywords:  has-patch => has-patch close 2nd-opinion


 After reading the spec closer, I see no need to change anything here.

 Specifically, the RFC quoted is specifying that the fields MAY be combined
 into a comma separated list(and that servers MUST present multiple headers
 in a form in which combining to a comma separated list will retain the
 original meaning), It is not dictating how a client must present the data
 given to a client (Excluding proxies, who must present the headers in the
 order given to them, and must not combine them, so as to preserve the
 meaning behind the message)

 Note, That this is different from ''unfolding'' where a header is split
 over multiple lines, and must be re-combined before presenting the field
 to clients.

Ticket URL: <http://core.trac.wordpress.org/ticket/13513#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list