Authorization header with Websockets not set if username+password are set in URL (as specified in RFC1738)

Not reproducible Issue #11014620


Sebastian M.
Feb 21, 2017
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

When opening a WebSocket like wss:// then no Authorization header for basic auth is set.

This can easily be tested on by reviewing the sent headers in the network tab of the dev tools.


0 attachments

    Comments and activity

    • Changed Steps to Reproduce

      Changed Steps to Reproduce

    • Where do you see this header in other browsers? Unless I am overlooking it, I don’t see it in the network tools in there, either.

    • Microsoft Edge Team

      Changed Status to “Not reproducible”

    • Hello,

      Thank you for providing this information about the issue. After thorough testing, we are unable to reproduce this problem in Edge with the information at hand. Please reopen this case when you can provide more details, such as screenshots.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in