[Webkit-unassigned] [Bug 80362] WebSocket: Client does not support 401 Unauthorized response.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Jul 26 02:13:16 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=80362
Varunan <svarunan at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |svarunan at gmail.com
--- Comment #6 from Varunan <svarunan at gmail.com> ---
@Ryan Slominski, I even have the same issue, Basic auth over websocket is not working in current Safari. Same works in other browsers. I thought of creating a new ticket, but just landed here.
In Safari
Basic auth over pure http works fine. But over websocket its not.
My Plan is to send user/password combo directly in websocket URL
`new WebSocket("ws://username:password@example.com")`, Once i receive http request with "Authorization" header validate it and upgrade to websockets in sockets server. But
This way http -> websocket upgrade happens only on auth validation.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170726/a6e3ae1f/attachment.html>
More information about the webkit-unassigned
mailing list