Right, after some considerable twiddling and tweaking I believe the issue is fixed. It was indeed a problem with the image proxy. Images that aren't served from a secure server are re-routed via a proxy that is secure so that the browser doesn't throw a wobbly about mixed secure / non-secure...