Incorrect content type in JsonService

[anonymous]

I used JsonService but I got an empty input stream in my servlet. I used TCP monitor to see what's happening, I found that the content type was incorrect.

Here is the capture of TCP monitor:

POST /lnp/resources/pages/Test.page?service=jsonrpc HTTP/1.1
Host: localhost:8080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q= 0.7
Keep-Alive: 300
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded
Content-Length: 46
Pragma: no-cache
Cache-Control: no-cache

{"params":["123","hi"],"method":"test","id":0}

I also found the root cause of this problem. The mimetype is not recognized by dojo.io.XMLHTTPTransport.

I change one line to get it work for me, but it may not be good enough for dojo project. My change is in BrowserIO.js;
The original line is:
http.setRequestHeader("Content-Type", kwArgs.multipart ? ("multipart/form-data; boundary=" + this.multipartBoundary) : (kwArgs.contentType | | "application/x-www-form-urlencoded"));

My new line is:
http.setRequestHeader("Content-Type", kwArgs.multipart ? ("multipart/form-data; boundary=" + this.multipartBoundary) : (kwArgs.contentType | | kwArgs.mimetype | | "application/x-www-form-urlencoded"));

if the core developers can review dojo code and use a consistent name for "contentType" or "mimetype".

Thanks.

Cliff Zhao

[sjmiles]

The contentType argument is intended to describe the outgoing request. The mimeType argument is inteded to describe the incoming response.

It can be a confusing distinction, especially because at first it appears odd to have a response type defined at request time. However, trying to detect or guess the proper response type from headers is less robust.

[anonymous]

Milestone 0.3release deleted