-
Notifications
You must be signed in to change notification settings - Fork 27.5k
Fix for issue #736: ngResource now accepts headers #965
Conversation
Thanks for your contribution! In order for us to be able to accept it, we ask you to sign our CLA (contributor's license agreement). CLA is important for us to be able to avoid legal troubles down the road. For individuals (a simple click-through form): For corporations (print, sign and scan+email, fax or mail): |
Oops, I'm sorry Max, I can see you already did sign the CLA, so please ignore my previous msg... |
Cool. Starting using angular today, found the problem with base authenticated rest resources this afternoon and found the patch this evening. Impressed..... |
ping... ? :) |
Me? Sent from my iPhone On 02.07.2012, at 18:10, Max Martinssonreply@reply.github.com wrote:
|
Any chance I can get an update on this one? I'm trying to integrate with a Rackspace ReST API and they auth using a custom X-Auth-Header. Is there a workaround without this patch? Or should I just patch my local copy? |
I am also curious of the status on this pull request. Similar to above, trying to integrate with a RESTapi that uses Basic Authentication. Would really like to be able to set the 'Authorization' header with a $resource. |
I'd also like to know the status of this issue. It's critical to be able to set authorization header (among others). |
sorry about the delay, working on merging it now |
MERGED |
Woohoo! Thanks @mhevery! |
Thanks, this is great. |
With this fix it is possible to specify HTTP headers in the actions parameter of ngResource.
For example, to be able to send conditional PUT requests you could specify:
As I understand it, this should resolve issue #736