I believe this issue is fixed now... feel free to give it a try and let me know if you're still having issues. Thanks to everyone for the detailed info-- reall

I believe this issue is fixed now... feel free to give it a try and let me know if you're still having issues. 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.