Repository navigation
Fix GH-25051: Restore TrueType font MIME detection - #25063
Conversation
Backport file/file@ba72caa54b, regenerate the bundled magic database, and add a regression test.
|
I'm not familiar enough with fileinfo to know if we normally do patches like this |
|
I've done patches like this in the past without any RM approval. |
I don't think RM approval is required, I just (wearing my normally developer hat) thought that the 8.6 RMs should be added as reviewers to make sure that they see this before branching 8.6.0 next week |
|
At least the diff matches the patch I sent to the list. So 👍 for the backport. FTR, even with this fix, TTF files get |
|
Drafted with an LLM; I ran every test below and reviewed the results myself.
|
…5073) Following the file 5.48 update and the fix in phpGH-25063, fileinfo reports TrueType fonts as font/ttf rather than the font/sfnt used in PHP 8.5 and earlier. Document this in the PHP 8.6 upgrade notes so applications with MIME type allow-lists, including WordPress font uploads, can account for the changed value. Closes php#25073
Following the file 5.48 update and the fix in GH-25063, fileinfo reports TrueType fonts as font/ttf rather than the font/sfnt used in PHP 8.5 and earlier. Document this in the PHP 8.6 upgrade notes so applications with MIME type allow-lists, including WordPress font uploads, can account for the changed value. Closes #25073
Backport file/file@ba72caa54b and regenerate the bundled magic database.
We need to record this to the magicdata.patch file as well since this is a difference between our version of libfile and the upstream.