heh, this is a server side issue and a problem with resources, not something clients are doing.
It starts off as a temporary server problem, but then becomes a bigger problem - for most users, the way the 502 page is cached.
I saw very few 502s yesterday, but tried to capture some of their headers, to me 304 seemed right, but 14400 seemed wrong, but that could very easily be because I had no idea what I was doing!
traffic.
I usually have the main index page open in another tab, so have been looking at the number of guests and users when I see some 502s, very roughly, so far the 502s seem to appear when the number of guests and users is low-ish rather than high-ish.