-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setRequestHeader #25
Comments
I agree, really need this functionality to authenticate against web services that require an API key etc. Any progress on this functionality? |
see #33, note this is only necessary across domains, as if you are on the same domain those headers automatically get set. Also note that it is only for ajax requests that it gets set as you can't set headers for jsonp requests |
Any possibility for more progress on #33? I need this to be able to content-negotiate on an API producing json or geojson by specifying 'accept' with value either 'application/json' or 'application/geo+json' |
PR #50 does fix this. |
This is not entirely clear to me, the docu says:
I thought this should work:
but probably I'm missing something |
Hi thanks for your share,
I think it will be nice to be able to .setRequestHeader from options{requestHeaders:{ key1 : value1, key2 : value2 }...}
I will test it and maybe do my first PR :).
The text was updated successfully, but these errors were encountered: