So, the roommate is on yayhooray.com.

It seems that they’re very anti-proxy, as when any proxy-specific header is found, they generate an HTTP 302 error with the IP the request came from – most people would just get a timeout page, really.

They must do it in the code (PHP, I think?) in the site, though, as the rest of the content is actually generated and sent after the header – so not a server config.

Got rid of via header and x-forwarded-for headers and it comes up.

Apparently they have a nemesis.  Guys, this isn’t a super-heroes club.