search

orbednetwork / chrome-rest-client

Automatically exported from code.google.com/p/chrome-rest-client
0 stars 0 forks source link

415 unsupported Media Type returned #97

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Submit a request via POST protocol
2. Specify the Content-Type as application/soap+xml
3. status code 415 (unsupported media type) returned

What is the expected output? What do you see instead?
I used the saved request in previous version and it worked before, but failed 
for current version (3.0.25)

On what operating system?
Mac OS X 10.8.2

Please provide any additional information below.

(This is an intranet request so it's not accessible via internet)
Header Raw : 
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 
4.0.30319.269)
VsDebuggerCausalityData: 
uIDPo7tMydOScXJDlTD0EEi+AYUAAAAAWSno4eWxyUCQsR0x3SvP2RJ8/qFnWc5FpCWrPNTirKIACQAA
Content-Type: application/soap+xml
SOAPAction: \"\"
Host: 10.48.62.70
Content-Length: 390
Expect: 100-continue
Connection: Keep-Alive

Original issue reported on code.google.com by CCT0...@gmail.com on 8 Nov 2012 at 4:18

GoogleCodeExporter commented 9 years ago 
As far as I know 415 is a server response. That's mean server doesn't recognize 
the request. What is it have something to do with the application?

Original comment by jarro...@gmail.com on 8 Nov 2012 at 7:38

GoogleCodeExporter commented 9 years ago 
We are getting same error in GET method. Same REST service was working fine in 
previous  version. Also if we hit the REST service in Chrome browser , it is 
giving the expected results

Original comment by swapnil....@gmail.com on 16 Nov 2012 at 12:03

Attachments:

GoogleCodeExporter commented 9 years ago 
Can you please make a fallowing:
Open inspector in the app, run the request, then check request and response 
headers for your request.
Next do the same but for request made in browsers tab (like in 
GET_request_in_browser screenshot). Compare headers and paste here results 
(difference). Maybe it give me clue what can be wrong with the app.

And maybe one more thing. Try to add content-type header to your service and 
add it to the response (application/json in this case). This error may appear 
when there is no content-type header in the response.

Original comment by jarro...@gmail.com on 16 Nov 2012 at 2:59

GoogleCodeExporter commented 9 years ago 
As for a lack of answer for a long time I'm closing this issue down.

Original comment by jarro...@gmail.com on 27 Mar 2013 at 3:37