Website: Stop responding with default MIME type - #1897
Merged
brandonpayton merged 1 commit intoOct 15, 2024
Conversation
It can interfere with more intelligent default handling by web browsers.
brandonpayton
added
[Type] Bug
brandonpayton
deleted the
hosting/let-browsers-guess-unknown-mime-type
branch
October 15, 2024 11:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation for the change, related issues
Responding with a default MIME type can interfere with more intelligent default handling by web browsers.
Implementation details
Update
custom-redirects-lib.phpto no longer respond with default MIME type when the type is not known.Testing Instructions (or ideally a Blueprint)
Tested manually on a stale Playground staging site.