Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upIgnore the Content-Type header completely for @font-face. #13931
Conversation
|
Could you explain how these changes unblock #13714 and what they are intended to do? |
|
I added a long commit message that should hopefully help. |
|
As discussed on IRC, I would like to see either the test removed along with all code that deals with the content type of font responses (along with an issue filed about implementing sniffing for fetch), or implementing sniffing for fetch properly. |
|
@bors-servo: r+ |
|
|
This matches the previous default (network.mime.sniff off) behaviour in all but one case: we will now accept a font without a `Content-Type` header, which would previously have been ignored.
|
Also removed the now-unused dependency on the mime crate. @bors-servo r=jdm |
|
|
|
@bors-servo: r- |
|
|
Ms2ger commentedOct 26, 2016
•
edited by larsbergstrom
This matches the previous default (network.mime.sniff off) behaviour in all
but one case: we will now accept a font without a
Content-Typeheader, whichwould previously have been ignored.
This change is