During the viral expansion of the “Richmond news paper editorial fiasco”, I submitted a post on the road.cc forum. In it, I had added an image linked straight from my server… What a great idea! Linking one of the most read cycling forum in the UK to my own domain! Lots of hits! … yeah, just that.

I definitely need to do some memory tweaking there, because that single image, requested by the road.cc page views, brought my server to its knees. Not – good.

I can’t recall how many times I’ve entered a domain name in a browser, say ‘domain.com’, only to wait 30 seconds and get an ugly 502 Bad gateway error in return. The problem? Enter http://domain.com instead of http://www.domain.com and see what happens.

1. you are served the expected website, the url stays the same
2. you are redirected to http://www.domain.com or some other url
3. you get a 502, Bad gateway timeout

I don’t know if it’s laziness, lack of knowledge or simply host providers being plain rubbish, but it’s an annoying problem that can be solved extremely simply!