Page MenuHomePhabricator

API returning non-RFC-compliant Content-Type header?
Closed, ResolvedPublic


Author: bm

The query API returns an extra semicolon in the the content-type header. Example:

With this URL:

this header:

Content-Type: text/xml; charset=utf-8;

is returned. My cursory reading of section 14.17 of RFC-2616 seems to confirm
that the last semicolon is disallowed. This broke one client I was using
(Common Lisp, Drakma, already patched).

Version: unspecified
Severity: minor
Platform: Other



Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 9:32 PM
bzimport set Reference to bz8673.
bzimport added a subscriber: Unknown Object (MLST).