Skip to content

"X-content-type-options" header missing from Reverse API response #3241

Answered by mtmail
dsantos747 asked this question in Q&A
Discussion options

You must be logged in to vote

The API doesn't serve any executable MIME types (e.g. javascript) so the security treat that a browser accidentially upgrades a non-executable as execuatable isn't given I think. I assume your Microsoft Edge Developer Tools only prints a notification or warning but the fetch request still works?

https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md#determining-whether-a-response-is-corb_protected

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by dsantos747
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #3240 on November 09, 2023 15:03.