[wp-trac] Re: [WordPress Trac] #3545: Content-Type header case sensitive

WordPress Trac wp-trac at lists.automattic.com
Wed Jan 10 14:16:46 GMT 2007

#3545: Content-Type header case sensitive
 Reporter:  johnleach                        |        Owner:  markjaquith
     Type:  defect                           |       Status:  assigned   
 Priority:  normal                           |    Milestone:  2.2        
Component:  General                          |      Version:  2.0.6      
 Severity:  normal                           |   Resolution:             
 Keywords:  headers mime type http wp-cache  |  
Changes (by markjaquith):

  * status:  new => assigned
  * owner:  anonymous => markjaquith
  * milestone:  2.0.7 => 2.2


 RFC2616 explicitly says that HTTP headers are case-insensitive.  That
 said, it doesn't hurt us to capitalize them as they are presented in the
 RFC.  Well-behaved clients won't care and lazy clients will more likely
 than not use the capitalization that the RFC uses.

 The only problem I see is that some of the instances in WP of "Content-
 type" are in external libraries like Snoopy or TinyMCE.  Changing those
 may present an added burden for maintenance.

 At any rate, 2.2 territory.

Ticket URL: <http://trac.wordpress.org/ticket/3545#comment:2>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list