I'm working on http://www.lovethesales.com - and have come up against an annoying issue.
As you'll probably be able to see for yourself on the homepage, sometimes, and intermittently, image requests will fail with a 502 Bad Gateway
error. This seems to happen in all browsers - (you can see the red failed requests in the Chrome developer tools, for example)
The resource in question /imageproxy can never return anything other than a 200, or a 304.
1) This page (set to show 500 results) never seems to have broken images, even though it's making similar / the same requests, but showing even more of them:
http://www.lovethesales.com/sales/?take=500
2) If you CTRL + refresh - it's always fine, it's only if you do a 'soft' headers refresh do you receive a 502 error. (Just clicking the refresh button)
The handler is a standard IHttpHandler, registered as follows:
<add name="ImageProxy" path="/home/imageproxy*" verb="*" type="LoveTheSales.Handlers.ImageProxy" resourceType="Unspecified" preCondition="integratedMode" />
Any advice / ideas on how to tack this down would be most appreciated.
Cheers, Dave
[EDIT] I have managed to recreate the issue on my test Azure instance (only me using it) - and, after turning on full web/request logging - I can see that the 502 requests are never even making it to my application - they aren't even in the logs. I guess this must be an Azure error?
[EDIT 2] This also happens on non-Imageproxy requests, so, simple static images too