# New Yorker site: Only with Firefox; what gives? **URL:** \ **Category:** Factual Questions\ **Created:** [December 1, 2013, 7:42pm UTC](https://boards.straightdope.com/t/new-yorker-site-only-with-firefox-what-gives/675233 "2013-12-01T19:42:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Musicat](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/musicat/32/20189_2.png) [@Musicat](https://boards.straightdope.com/u/Musicat)\ **Post date:** [December 1, 2013, 7:42pm UTC](https://boards.straightdope.com/t/new-yorker-site-only-with-firefox-what-gives/675233/1 "2013-12-01T19:42:42Z")
It’s possible that this situation is temporary, and may clear up or change before anyone answers, but I’m curious what might be going on. I _can_ reach [www.newyorker.com](http://www.newyorker.com) or [newyorker.com](http://newyorker.com) or [http://newyorker.com](http://newyorker.com) using Firefox with no problems. No, I don’t think it is being cached locally, and I can navigate many pages at that site with no errors. Each of the New Yorker URLs causes a “Aw, Snap!” error in Chrome. Each of the New Yorker URLs causes a “…cannot open the Internet site…” in IE 6. I can **not** ping or tracert [newyorker.com](http://newyorker.com) (205.217.104.30), getting timeout errors. I **can** ping or tracert [www.newyorker.com](http://www.newyorker.com) (198.47.108.74) with zero loss, 27ms time. All of these tests are being performed thru the same Internet cable connection on a PC running XP SP2. What gives? Why is Firefox the only browser that can get through? ---
**Author:** ![The\_Niply\_Elder](https://avatars.discourse-cdn.com/v4/letter/t/8e8cbc/32.png) [@The\_Niply\_Elder](https://boards.straightdope.com/u/The_Niply_Elder)\ **Post date:** [December 1, 2013, 7:55pm UTC](https://boards.straightdope.com/t/new-yorker-site-only-with-firefox-what-gives/675233/2 "2013-12-01T19:55:04Z")
I just opened the site with safari on my iPad although it asked me to rotate my device (wtf?) ---
**Author:** ![Musicat](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/musicat/32/20189_2.png) [@Musicat](https://boards.straightdope.com/u/Musicat)\ **Post date:** [December 1, 2013, 8:33pm UTC](https://boards.straightdope.com/t/new-yorker-site-only-with-firefox-what-gives/675233/3 "2013-12-01T20:33:57Z")
> [@The\_Niply\_Elder](#): > > I just opened the site with safari on my iPad although it asked me to rotate my device (wtf?) What does “rotate a device” mean? Do a pirouette? ---
**Author:** ![Musicat](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/musicat/32/20189_2.png) [@Musicat](https://boards.straightdope.com/u/Musicat)\ **Post date:** [December 1, 2013, 8:42pm UTC](https://boards.straightdope.com/t/new-yorker-site-only-with-firefox-what-gives/675233/4 "2013-12-01T20:42:06Z")
Maybe it means to change your display from portrait (vertical) to landscape (horizontal) for better formatting? ---
**Author:** ![njtt](https://avatars.discourse-cdn.com/v4/letter/n/ecd19e/32.png) [@njtt](https://boards.straightdope.com/u/njtt)\ **Post date:** [December 1, 2013, 9:17pm UTC](https://boards.straightdope.com/t/new-yorker-site-only-with-firefox-what-gives/675233/5 "2013-12-01T21:17:31Z")
I can open the site in FF, IE 11 and Chrome, but in the latter two it popped up a video ad overlay a second or so after loading. I have Flashblock running in FF, so presumably that is what stopped it there. I am guessing yo have Adblock of Flashblock running in Firefox, and maybe your Flash needs updating for the other two browsers. (The ad can actually be closed quite easily, and it seems to be muted by default, so it is merely obnoxious rather than truly evil.) ---
**Author:** ![tellyworth](https://avatars.discourse-cdn.com/v4/letter/t/977dab/32.png) [@tellyworth](https://boards.straightdope.com/u/tellyworth)\ **Post date:** [December 1, 2013, 10:15pm UTC](https://boards.straightdope.com/t/new-yorker-site-only-with-firefox-what-gives/675233/6 "2013-12-01T22:15:51Z")
Firefox is notorious for its DNS cache. It’s likely that FF cached an IP address for [newyorker.com](http://newyorker.com) that happened to work; the other browsers and tools, behaving correctly, did not. That site appears to use an edge cache, which should mean that it effectively has many IPs and traffic is routed to the nearest cache. But I think something might not quite be configured correctly on their side.