nice work
Thanks, but I might have opened up a new, but hopefully smaller, bag of worms in the fix. There was a header that AT&T didn't like, and putting the arc server behind a nginx reverse proxy fixed that. However, there seems to be a thing or two amiss with the arc server and nginx, which I am now trouble-shooting. ATM it's behind nginx, but I might have to revert back for a bit and troubleshoot some more if I can't get the two to stay happy.
I did get a few "502 bad gateway" errors from nginx this morning (about nine-ish GMT +1) which meant I couldn't visit Hubski. I take it those were because you were fixing things?
Well, technically, it was because I was breaking things. :) If you want the gory details, I put Hubski's arc server behind a nginx proxy. Unfortunately, the arc server throttles an IP making too many requests, and I didn't anticipate that since it was being fed by the nginx proxy, it would do so for all requests. I went to bed and Hubski essentially started throttling itself to death. :/ Everything is happy now. My next step is to get nginx to serve most of the static content, which it can probably do faster than the arc server.