I just did a slightly more reliable test: disabled js in the FF settings (about:config→javascript.enabled=false). And the PDF was fetched and rendered with some delay.
It is clear from wget that the server is at least willing to push html,js,garbage that masquerades as a “pdf”. But I believe you are correct; that w/this sample URL, Mozilla is getting a true PDF based on some opaque judgment by the server.
So that URL turns out to be a bad example. I see this all the time though. I will have to start collecting more PDF URLs that push shenanigans until one reproduces Mozilla’s anti-user behavior.
I just did a slightly more reliable test: disabled js in the FF settings (
about:config→javascript.enabled=false). And the PDF was fetched and rendered with some delay.It is clear from wget that the server is at least willing to push html,js,garbage that masquerades as a “pdf”. But I believe you are correct; that w/this sample URL, Mozilla is getting a true PDF based on some opaque judgment by the server.
So that URL turns out to be a bad example. I see this all the time though. I will have to start collecting more PDF URLs that push shenanigans until one reproduces Mozilla’s anti-user behavior.