Mozilla performing pdf.js DNS queries?

Hi,

Whilst rummaging through some DNS (dnsmasq) logs I've noticed quite a
decent amount of queries for pdf.js from what appear to be mozilla browsers.

Seems rather odd that it is performing DNS queries for a internal PDF
viewer.

Has anyone else come across these lookups?

Kind regards,

Seth

Pdf is quite a standard. One might wonder what it cannot do. One could call it evil.

http://superuser.com/questions/368486/link-to-image-within-pdf-and-have-the-image-displayed

David Hofstee

Deliverability Management
MailPlus B.V. Netherlands (ESP)

-----Oorspronkelijk bericht-----

David Hofstee schreef op 13-11-2014 14:39:

Pdf is quite a standard. One might wonder what it cannot do. One could call it evil.

Link to image within pdf, and have the image displayed? - Super User

Ah yes, a image within a PDF could definitely do this I suppose. I just
thought it odd that the browser would leak this out.

dnsmasq[3151]: query[A] pdf.js from 10.6.24.11
dnsmasq[3151]: query[AAAA] pdf.js from 10.6.24.11
dnsmasq[3151]: query[A] pdf.js from 10.6.24.11
dnsmasq[3151]: query[AAAA] pdf.js from 10.6.24.11

This could become a whole can of worms if a .js TLD ever makes it to the
internet and registers this domain name.

We see this from Ubuntu terminals running Mozilla Firefox 33.0

Best regards,

Seth

Totally wild shot in the dark - recent Mozilla have an onboard PDF viewer
written in javascript called pdf.js

http://en.wikipedia.org/wiki/PDF.js

It's callable from within other javascript via chrome:// or resource://
references, but sometimes people don't get it right:

http://superuser.com/questions/614002/how-to-open-pdf-js-in-firefox-via-chrome-url

My guess is that somebody else didn't quite get it right, and is trying to
get to the hostname when they intended to get to the javascript.....

<@darq> 17:40 < ircperson> oof. apparently .prod is a TLD now
<@darq> 17:40 < ircperson> and a friend's environment is basically on fire.
<@darq> HAHAHA
     
/kc

https://www.icann.org/resources/pages/name-collision-2013-12-06-en

Regards,
-drc

https://bugzilla.mozilla.org/show_bug.cgi?id=1098415 has been filed to
track this issue.

~reed

I have personally declared FF33 to be a pinnacle disaster in a long string of disasters.

I don't have the wherewithal, time, or desire to sort out what new breakages there are and which are "just" unfortunate coincidences.

Most annoying is that with either FF or TB running, my windows 8.1 machine hangs for minutes at a time.