Unable to set content-type request header for delete method.

[jaswant-ghuraiya]

I tried as below approach-

$httpProvider.defaults.headers["delete"] = {'Content-Type': 'application/json;charset=utf-8'};

My request doesn't have any body. And the actual request header is always taking "content-type" as "text/plain".

[kdekooter]

Having similar issues with put and post. Content-Type of the request is always set as application/xml

[michelsalib]

I am having the exact same issue. Impossible to change the Content-Type of a DELETE request.

[d13r]

I think if there is no request body (data parameter) the Content-Type header is deliberately removed:

angular.js/src/ng/http.js

Line 638 in b99d064

if (lowercase(header) === 'content-type') {

The code above worked for me when the data parameter is set.

[arciisine]

Running into the same issue as well. When working with a framework that expects content-type for all HTTP verbs, this is an issue.

Also, since neither GET and DELETE support content, I would expect them both to work the same way.

[david-driscoll]

I wonder if there is a specific reason the content-type is stripped? JQuery doesn't make that assumption for example. This was a frustrating little feature to find out.

[Grummle]

Is DELETE supposed to have Content-Type always set?

When using $http.delete(url) we've been seeing the following:

Chrome 28 (and some lower):

Content-Type:application/xml

FireFox 22:
Content-Type text/plain; charset=utf-8

IE 10:
Content-Type text/plain;charset=UTF-8

The Content-Type header throws our conneg for a loop. Perviously using:

$.ajax({url:url,type:'DELETE'});

We didn't have this issue and no 'Content-Type' was specified.

Accept:*/*
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8
Cache-Control:no-cache
Connection:keep-alive
Host:localhost
Pragma:no-cache
User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36
X-Requested-With:XMLHttpRequest

The issue seems to be with this piece of code in $httpBackend:

      xhr.send(post || '');

If you simply change that to something like:

if(post) xhr.send(post);
else xhr.send();

Then all is well with the world. I've tested it on the 1.1.5 tag and all the tests pass in Mac Chrome/Safari include e2e, but I haven't a clue how to write tests for it or I'd submit a pull request. Currently we are forced to run a modifed version of angular, but we'd like to run the google cdn version. Any suggestions?

[mikeobrien]

👍

[mariussoutier]

+1

[muratcorlu]

+1

[muratcorlu]

xhr.send(post || null);

works too. I hope somebody merges this fix to master.

[eranation]

👍

[srawlins]

+1

[kdekooter]

OK. It's been 5 months now. It would be nice to get some kind of feedback from one of the core committers.