Content-Type is set by Default (application/x-www-form-urlencoded), but should not be

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a Get request.
2. Specify just only Accept header. No Content-Type required:
3. Send request

Expected response: Status: HTTP 200 Ok.
Advanced REST client for Google Chrome - version 2.1.

Here is what we have (captured by firebug net monitor)

Accept:application/vnd.tomtom.device-content+xml;version=1
Accept-Charset:UTF-8,*;q=0.5
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8,ru;q=0.6
Connection:keep-alive
Content-Type:application/x-www-form-urlencoded
Cookie:MUID_TRAIL=VG_0001%2CKV9B12LE0022%2Cdev_01%2Cundefined%2Cundefined%2Cunde
fined%2Cundefined%2Cundefined%2Cundefined%2Cundefined%2Cundefined%2Cundefined%2C
undefined%2Cundefined%2Cundefined%2Cundefined%2Cundefined%2Cundefined%2Cundefine
d%2Cundefined
Host:tt-vger-vm-xp:8080
User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like 
Gecko) Chrome/18.0.1025.142 Safari/535.19

You can see there is "Content-Type:application/x-www-form-urlencoded"
But my application does not support this one.

Just to compare - here is a request header for REST client in Firefox for the 
same service.

Accept  application/vnd.tomtom.device-content+xml;version=1
Accept-Encoding gzip, deflate
Connection  keep-alive
Host    tt-vger-vm-xp:8080
User-Agent  Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 
Firefox/11.0

This case (without Content-Type header) the request is produced properly.

Original issue reported on code.google.com by vovik...@gmail.com on 2 Apr 2012 at 4:19

[GoogleCodeExporter]

Should be fixed in next release. 

Original comment by jarro...@gmail.com on 4 Apr 2012 at 6:49

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by jarro...@gmail.com on 4 Apr 2012 at 6:49

[GoogleCodeExporter]

Original comment by jarro...@gmail.com on 11 Apr 2012 at 9:21

• Changed state: Fixed