whatwg / whatwg/fetch

Header to opt out of opaque redirect

Open
#601 63 comments 65 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

addition/proposal needs implementer interest topic: redirects
Dominant language
HTML
Stars
2.3k
Forks
403
Avg merge
21h 16m
Merged PRs (30d)
4

Description

Something like Access-Control-Allow-Visible-Redirect: *

This would make a redirect responses visible. If the request was cross-origin, it would still have to pass existing CORS checks, and would be filtered accordingly.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the proposed header and the 63-comment discussion to understand the unresolved behavior around redirects and CORS. Done would require an agreed Fetch Standard design and corresponding specification changes, but the issue names no files, tests, or implementation entry points.

Written by the indexing model from the issue text.

Assessment

Domain
api, security, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.