HTTP 201 Created is not handled

[okigan]

This is similar to #2572, but with different fix proposal:

Per the HTTP spec POST request returns '201 Created' with URI for the resource in the "Location" header field.

Right now this situation is not handled by $resource factory. Also the location property is invaluable to get updated state of the resource.

So propose to make the "Location" property available from the $resource service.

[okigan]

@btford per original closure of #2572 please review this issue.

[okigan]

Reference to the HTTP standard: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

[linclark]

As you mention, the original issue was proposing something different.

What you propose—getting the Location header after a successful call to $resource::save()—is already supported. I put together a Plunker to demonstrate.

If you have followup questions about this, I'd suggest posting them on Stack Overflow because there are more folks answering support questions there.

[okigan]

@linclark thanks for idea in Plunker, but it forces code duplication at every location the resource is saved.

Is there a way to add the code that gets http location header to the $resource itself ?