MicrosoftEdge / MicrosoftEdge/WebView2Feedback
CreateWebResourceResponse with content-encoding gzip
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
we are trying to directly pass gz encoded data via CreateWebResourceResponse by adding a header
Content-Encoding: gzip
and setting the gz content as payload.
In request headers there is no accepted encoding header, just passing Content-Encoding results in garbage results...
Are we doing something wrong or are those things not possible ?
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 with CreateWebResourceResponse and the request headers to verify how Content-Encoding: gzip is handled when no accepted encoding is present. Done means confirming whether gzipped payloads are supported and documenting the required headers or the limitation.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100