Skip to content
This repository has been archived by the owner on Mar 1, 2021. It is now read-only.

Content-Type request header not sent #88

Open
jmerhar opened this issue Feb 21, 2013 · 2 comments
Open

Content-Type request header not sent #88

jmerhar opened this issue Feb 21, 2013 · 2 comments
Assignees

Comments

@jmerhar
Copy link

jmerhar commented Feb 21, 2013

I noticed a very strange bug:

  1. I make a POST request with Content-Type "application/x-www-form-urlencoded" and Accept set to a vendor media type.
  2. The request executes fine and the server returns a response with Content-Type set to the same vendor media type.
  3. I then press "Send" again, with exactly the same settings, and the Content-Type header is no longer sent with the request.
  4. This happens for every subsequent request until I change the Content-Type of the response to something like "text/html". After that it starts working again.

Does the Content-Type response header of the previous request somehow affect the Content-Type request header of the next one?

@shveik
Copy link

shveik commented Mar 29, 2013

my issue with content type is similar, it actually is set to application/xml if left blank

@ghost ghost assigned ahmadnassri Apr 3, 2013
@ahmadnassri
Copy link
Owner

both issues are certainly not the expected behaviour ... it may be related to new versions of Chrome ... currently investigating.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants