Skip to content

feat(network): support multiple httpCredentials for different origins#41822

Open
Gby56 wants to merge 1 commit into
microsoft:mainfrom
Gby56:feat-22013
Open

feat(network): support multiple httpCredentials for different origins#41822
Gby56 wants to merge 1 commit into
microsoft:mainfrom
Gby56:feat-22013

Conversation

@Gby56

@Gby56 Gby56 commented Jul 16, 2026

Copy link
Copy Markdown

Summary

  • Allow httpCredentials to be a single object or an array of origin-scoped credentials (HttpCredentials | HttpCredentials[])
  • Chromium, BiDi, and APIRequest select credentials by request origin; Firefox juggler updated for multi-credentials (needs browser roll); WebKit rejects arrays with more than one entry

Fixes #22013

Made with Cursor

Allow httpCredentials to be a single object or an array of origin-scoped
credentials. Chromium, BiDi, APIRequest, and Firefox (juggler) pick by
origin; WebKit rejects multi-entry arrays.

Fixes: microsoft#22013
Co-authored-by: Cursor <cursoragent@cursor.com>
@dgozman

dgozman commented Jul 16, 2026

Copy link
Copy Markdown
Collaborator

@Gby56 Could you please comment on the issue and explain your usecase? Although this seems theoretically useful, in practice we haven't seen any real scenarios that would justify the complexity (this PR, for example, touches over 700 lines in 39 files).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] Support of multiple HTTP credentials for different origins

2 participants