You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Allow setting of custom headers in client requests #82
Various authentication mechanisms and state mechanisms use headers to communicate with the server. One simple method to support these is to be able to add arbitrary headers to a given connection.
Activity
sta commentedon Oct 20, 2014
I don't plan to support user custom headers for now.
samuelgoldenbaum commentedon Aug 11, 2015
Really do need this for jwt tokens
tewarid commentedon Dec 30, 2015
Elaborating on the previous comment, it will be really nice to be able to set bearer tokens as described in RFC 6750.
For example
ramonchis commentedon Feb 5, 2016
Hi. For my project, I implemented changes to the library that allow setting custom HTTP headers.
Is this something that you are willing to incorporate?
If so, how would you prefer to get the modified code? Diffs? Full source for the changed file?
Thanks,
Ramonchis
GibbOne commentedon Apr 21, 2016
@ramonchis do you implement client and server side? Do you implement JWT?
NikkyAI commentedon Jan 8, 2021
is there any workaround for this in use currently ?
or was this possibly added as a feature and forgot to close this issue ?
tewarid commentedon Jan 8, 2021
Please see #22 (comment).
NikkyAI commentedon Jan 8, 2021
cool, sadly i do not have the option to change the dependecy currently, otherwise i would use WebSocket4Net