-
Notifications
You must be signed in to change notification settings - Fork 356
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
extra-headers still not supported in browser #554
Comments
The documentation could definitely be improved here 👍 |
And what about |
Ah I see (for future reference, more testing and notes: https://trello.com/c/7oqnpaxT/88-verify-that-extraheaders-is-actually-still-100-fixed-for-browser-usage-in-socket-io-client-engine-io-client-and-if-so-1-update-t) We have some code that looks for a "nosession" header in order to determine whether to log warnings or not when the cookie can't be used.
@darrachequesne So I'm guessing maybe if we named it "Authorization" we'd have better luck? (I'll take that for a spin and post back-- just making sure that's the intended behavior.) @gjuchault re what's documented now: https://github.com/socketio/engine.io-client/tree/be4c9067b548f3e27dd1889e4094aff5b6d9eecb#nodejs-with-extraheaders |
Aside: for other folks finding this looking for an immediate answer, note that |
Update: |
it works, you can print socket.handshake.headers['x-clientid'] on server. |
you can send credentials like this
|
It appears that those lines
engine.io-client/lib/socket.js
Lines 99 to 103 in 1519765
The way to use extraHeaders in Node is:
The way to use extraHeaders in Browser is (#536 (comment)):
The text was updated successfully, but these errors were encountered: