You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The listed features are documented sufficiently on MDN
BCD is updated
Interactive example and data repos are updated if appropriate
The content has been reviewed as needed
For folks helping with Firefox related documentation
Set bugs to dev-doc-complete
Add entry to Firefox release notes if feature is enabled in release
Add entry to Firefox experimental features page if feature is not yet enabled in release
Features to document
I think we might need to add experimental feature behind pref: network.cors_preflight.authorization_covered_by_wildcard
# When the Access-Control-Allow-Headers is wildcard (*), whether to allow
# CORS-protected requests with the Authorization request header.
- name: network.cors_preflight.authorization_covered_by_wildcard
Check content open issues to see if any pertain to the subject matter. If there are any that can be closed because of the work, do so. If there are any that can be fixed relatively quickly because of the knowledge from completing this issue and you have time, feel free to go ahead and fix them.
Check if glossary updates are required for the feature you're documenting - whether an existing term needs to be updated or a new term should be added.
Check if BCD update means that content pages need to have experimental markup removed or deprecated markup added (front matter tags and macros).
The text was updated successfully, but these errors were encountered:
hamishwillee
changed the title
Don't think anything needs to be done here, but worth a check https://bugzilla.mozilla.org/show_bug.cgi?id=1687364
[Not release] HTTP Access-Control-Allow-Header can't be wildcarded for authorization directive
Jun 9, 2023
FWIW, this behavior is not going to ship with Firefox 115. It's going to be available behind a pref. We're estimating that this may cause compatibility issues and are currently debating a coordinated launch across browser vendors. whatwg/fetch#1278 has more.
Acceptance Criteria
For folks helping with Firefox related documentation
dev-doc-complete
Features to document
I think we might need to add experimental feature behind
pref: network.cors_preflight.authorization_covered_by_wildcard
There is also https://bugzilla.mozilla.org/show_bug.cgi?id=1687364#c4 which indicates we might need to update Access-Control-Expose-Headers to remove comments around use of the authorization header.
Querying this in https://bugzilla.mozilla.org/show_bug.cgi?id=1687364#c41
Related Gecko bugs
https://bugzilla.mozilla.org/show_bug.cgi?id=1687364
Other
The text was updated successfully, but these errors were encountered: