MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Problem/Bug]: Custom schemes don't work with the js fetch() api
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
I you register a custom scheme and try to use it with the js fetch() api you get an unauthorized error in js
fetch('custom://dir/file.html');
Importance
Moderate. My app's user experience is affected, but still usable.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
No response
SDK Version
No response
Framework
Win32
Operating System
Windows 10
OS Version
No response
Repro steps
Register a custom scheme and try to use it with fetch() js API
Repros in Edge Browser
Not Applicable
Regression
No, this never worked
Last working version (if regression)
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Win32 WebView2 case from the issue: register a custom scheme, then call fetch('custom://dir/file.html') and capture the unauthorized response. Trace the custom-scheme registration and fetch handling; done means fetch succeeds for registered custom schemes without the unauthorized error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100