#4419 Charset is not recognized when specified as quoted string

obsolete: 8.5.7
closed-fixed
9
2009-09-10
2009-09-03
No

The http package may not correctly perform encoding conversion when the charset is specified as a quoted string, e.g. when the Content-Type header is specified as; text/xml; charset="UTF-8".

In case of the example above, the charset element in the state array ends up getting the value "utf-8" (including the quotes). This is interpreted by http::CharsetToEncoding as binary, resulting in no encoding conversion taking place.

The way I read RFC 2616 it is legal for charset to be specified as a quoted string.

Discussion

  • Donal K. Fellows

    Agreed. My reading of the RFC also leads me to that conclusion.

     
  • Donal K. Fellows

    • priority: 5 --> 9
     
  • Donal K. Fellows

    • assigned_to: patthoyts --> dkf
    • status: open --> closed-fixed
     
  • Donal K. Fellows

    (fixed for 8.5 and HEAD)

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks