JSON-RPC service SHOULD permit application/json-rpc for Accept and Content-Type
headers according to the spec
-------------------------------------------------------------------------------------------------------------
Key: SHINDIG-1142
URL: https://issues.apache.org/jira/browse/SHINDIG-1142
Project: Shindig
Issue Type: Bug
Reporter: Kartick Vaddadi
According to the JSON-RPC over HTTP spec at
http://groups.google.com/group/json-rpc/web/json-rpc-over-http:
Regardless of whether a remote procedure call is made using HTTP GET or POST,
the HTTP request message MUST specify the following headers:
* Content-Type SHOULD be 'application/json-rpc' but MAY be
'application/json' or 'application/jsonrequest'
* [...]
* The Accept MUST be specified and SHOULD read 'application/json-rpc' but
MAY be 'application/json' or 'application/jsonrequest'.
Shindig should accept application/json-rpc rather than just application/json.
This bug occurs on the production orkut JSON-RPC service at
orkut.com/social/rpc — I get a message like this:
{"message":"badRequest: Invalid batch - Unsupported Content-Type
application/json-rpc. One of application/json, text/x-json,
application/javascript, application/x-javascript, text/javascript,
text/ecmascript, multipart/form-data is required","code":400}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
