Gervase Markham wrote:
Douglas Crockford wrote:
I have modified the JSONRequest proposal so that the Content-Type in
both directions must be application/json/request.
Er, why? Having two slashes in a content type is either extremely weird
or completely illegal (glancing at the RFC, I'm not certain which).
http://www.mhonarc.org/~ehood/MIME/2046/rfc2046.html
RFC 2616 states:
media-type = type "/" subtype *( ";" parameter )
type = token
subtype = token
token = 1*<any CHAR except CTLs or separators>
separators = "(" | ")" | "<" | ">" | "@"
| "," | ";" | ":" | "\" | <">
| "/" | "[" | "]" | "?" | "="
| "{" | "}" | SP | HT
And RFC 2045 says something very similar. So the second '/' is indeed
illegal.
If application/json isn't acceptable (though I don't know why it
wouldn't be), then try a hyphen instead: application/json-request
--
Lachlan Hunt
http://lachy.id.au/
