Facebook fails to load if using br encoding
Yesterday I opened Facebook.com and saw this: "Þk¢¨hõpFrÒê?Ð??×c÷¼ª~ß÷ÓT?L²æŠ?Á,ùZ> ”%YÉ –ík??$A??IШ`¯whªß¥Ð”û~SüzÿZ&¬??;…»TtzìV?Ë!¨?Øí–ÞKÿä}ió%Û9’=“#Û??:Æ=Ç^xðõ%k4¸äqh`5?B{ @Ø´‹??-`ÕÍÙÊešr“¢K›¢éRvñÿ[ë3²;7l4°ð?7?PÈ5bσê3?B¨ªîéôŸé?‘]0*q‚ÈÇéüU??Âä1̬÷~‹H???ZÓÎD6sö¢ƒz?ª—Àfqhÿϯ5?«??f$&cù?Ø]Ûg1`@”@“Á 3?(u~â?0iø?Ò‚zé??ŽÛ??ïåÁϼï—ïðÖŸ~?+?kÞ:ï|?“B‡†£Òâ8Ì*™^‘ÚgƆà*¬}Öüˈ+©…?¢·?ò#z»þ2É«ù©qQ†ƒ˜’KíóáW?þð‹ã?oõ v-±?·‹_?oþÉ7Ñn›àj#ô ‡¸â'¼ (??ËØ?¶a÷i_Œ'|³‹?²–?Á:ÌR™Â6Üt?†G=|¸ƒuxøüqèËýßôo‘ÿ-5=Žª¿?™Fœ MO¿h ..." and much more (copy-pasted this because for some reason I couldn't upload a screenshot).
After a bit of digging I found the suggestion to 'Reset' to the default values the network.http.accept-encoding and network.http.accept-encoding.secure settings. In my case they were already set to the default values, so I started messing with them and found this:
network.http.accept-encoding.secure - gzip, deflate, br means https://www.facebook.com is shown as in the example;
network.http.accept-encoding.secure - gzip, deflate means https://www.facebook.com is shown as it should be;
The same problem with the same solution happened on the other PC in my house.
My questions are: What could cause this behavior? What are the disadvantages of not having br as an option for encoding? Are there any security risks?
Modified by blue_alien_bg
Chosen solution
Firefox 44+ accepts a new kind of encoding (compression) called Brotli (br) for secure connections and Facebook turned on Brotli encoding a couple days ago.
Kapsersky doesn't know about this encoding and strips it from the HTTP response headers if you have "Inject script" checked in Kapsersky Settings -> Additional -> Network -> Traffic Processing
See also https://forum.kaspersky.com/index.php?showtopic=351027
Read this answer in context 👍 2All Replies (2)
Chosen Solution
Firefox 44+ accepts a new kind of encoding (compression) called Brotli (br) for secure connections and Facebook turned on Brotli encoding a couple days ago.
Kapsersky doesn't know about this encoding and strips it from the HTTP response headers if you have "Inject script" checked in Kapsersky Settings -> Additional -> Network -> Traffic Processing
See also https://forum.kaspersky.com/index.php?showtopic=351027
James said
Firefox 44+ accepts a new kind of encoding (compression) called Brotli (br) for secure connections and Facebook turned on Brotli encoding a couple days ago. Kapsersky doesn't know about this encoding and strips it from the HTTP response headers if you have "Inject script" checked in Kapsersky Settings -> Additional -> Network -> Traffic Processing See also https://forum.kaspersky.com/index.php?showtopic=351027
Yes, that definitely works. I told Kaspersky not to scan encrypted connections and reset the network.http.accept-encoding.secure to its default value and Facebook opens perfectly.