Open jmerhar opened 11 years ago
my issue with content type is similar, it actually is set to application/xml if left blank
both issues are certainly not the expected behaviour ... it may be related to new versions of Chrome ... currently investigating.
I noticed a very strange bug:
Does the Content-Type response header of the previous request somehow affect the Content-Type request header of the next one?