Hey, I'm the creator of the blogging platform he's running on and am trying to replicate this. Do you have cookies or js off or any other notable change from stock?
I do use a few addons (Flashblock, Adblock plus, Ghostery) that possibly could cause side effects, but since Chrome also causes problems for some I doubt that it's a Firefox specific bug.
Thanks to everyone for the detailed info-- really helped me a lot.
For those interested, here's what happened:
When someone goes to a SETT blog, the first thing we do is fire off an ajax call to see if we can set a 3rd party cookie. If we can't, we bounce to a page on sett.com that sets a cookie and then redirects back. In some cases, like Safari with default settings, this allows us to use a 3rd party cookie.
To prevent infinite looping in cases where 3rd party cookies can't be accessed, we add a query string to the URL, telling SETT to skip the cookie check.
However, the old way we were doing it was just appending ?_ to the URL, rather than parsing it out and taking into consideration the query string of the URL.
This URL was submitted with a trailing ?, which made the query string ??_, which didn't properly skip the cookie check. Thus... infinite refreshes.