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

[WordPress Trac]

#13513: Processing HTTP Headers violates RFC 2616
--------------------------+-------------------------------------------------
 Reporter:  hakre         |       Owner:  dd32     
     Type:  defect (bug)  |      Status:  new      
 Priority:  normal        |   Milestone:  3.0      
Component:  HTTP          |     Version:           
 Severity:  normal        |    Keywords:  has-patch
--------------------------+-------------------------------------------------
 Quote:

 {{{
  Multiple message-header fields with the same field-name MAY be
    present in a message if and only if the entire field-value for that
    header field is defined as a comma-separated list [i.e., #(values)].
    It MUST be possible to combine the multiple header fields into one
    "field-name: field-value" pair, without changing the semantics of the
    message, by appending each subsequent field-value to the first, each
    separated by a comma. The order in which header fields with the same
    field-name are received is therefore significant to the
    interpretation of the combined field value, and thus a proxy MUST NOT
    change the order of these field values when a message is forwarded.
 }}}

 Summary:

 - Multiple message-header fields with the same field-name ''MAY'' be
 present[[BR]]
 - It ''MUST'' be possible to combine the multiple header fields into one
 "field-name: field-value" pair[[BR]]

 Currently the code is creating an array instead of a comma separated list.

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