meh / smart-referer

MOVED to GitLab: https://gitlab.com/smart-referer/smart-referer/
https://gitlab.com/smart-referer/smart-referer/
Other
95 stars 11 forks source link

On Firefox 59.0 Smart Referer prevents playing Facebook videos #96

Closed AntonioRedondo closed 6 years ago

AntonioRedondo commented 6 years ago

Hi meh,

It looks like Smart Referer prevents videos being played on Facebook. This was not the case just a week ago. Facebook has made some change and know it requires the referer being sent in order to play videos. As soon as I disable the add-on videos play normally. I've added the exceptions *.fbcdn.net and *.facebook.com to the add-on options but videos still don't play.

Am I missing something?

l0gik commented 6 years ago

I can verify this issue, appearing recently (FWIW it appears to be CORS-related). However, unlike OP I was able to restore video playback by adding *.facebook.com as the source, and video.*.fna.fbcdn.net as the destination to the Exceptions list. NB: I haven't mapped out the FB CDN servers or anything, so that destination might be too specific depending on where the video is hosted.

ntninja commented 6 years ago

Thanks @l0gik! I cannot verify this, but if @AntonioRedondo can test this I think we can add it to the whitelist anyway.

AntonioRedondo commented 6 years ago

Hi guys, thanks for the quick reply. I just tried adding *.facebook.com as the source, and video.*.fna.fbcdn.net as the destination, but it didn't work. I also tried *.fna.fbcdn.net. Still no luck. However, if the destination is only *.fbcdn.net then videos reproduce again.

vertigo220 commented 6 years ago

I just ran into this on Waterfox 56.2.0. I added .facebook.com as the source and .fbcdn.net as the destination and it worked. I did it this way, before even coming here, because I don't see the point in restricting it, since they're both facebook, and doing so will only cause it to break if/when it doesn't use the same exact server (e.g., mine was video-ort2-1.xx.fbcdn.net). Using *.fbcdn.net should prevent issues in all cases. This should probably be added to the built-in whitelist, since as I said, they're both facebook anyway, so there's not really a reason not to.

ntninja commented 6 years ago

Thanks for your feedback everybody *.facebook.com>*.fbcdn.net has been added to the whitelist!