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

WordPress Trac wp-trac at lists.automattic.com
Mon May 24 12:14:03 UTC 2010

#13513: Processing HTTP Headers violates RFC 2616
 Reporter:  hakre         |       Owner:  dd32          
     Type:  defect (bug)  |      Status:  new           
 Priority:  normal        |   Milestone:  Future Release
Component:  HTTP          |     Version:  3.0           
 Severity:  normal        |    Keywords:  needs-patch   
Changes (by hakre):

  * version:  => 3.0


 A first patch. There is another issue regarding the response status code
 and message by injecting header not containing any colons. That is somehow
 already prevented by the "redirection" handling (which will only return
 the last status field and/or the injected one as I just see, need to
 update the patch).

 I'll update the current patch to remove my handling of that again.

 Additionally there is another issue with tolerant status line parsing we
 do not cover:

 Clients SHOULD be tolerant in parsing the Status-Line [...]. In
 particular, they SHOULD accept any amount of SP or HT characters between
 fields, even though only a single SP is required.
 Source: 19.3 Tolerant Applications / RFC 2616

 We just do an explode on a single space.

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

More information about the wp-trac mailing list