I'm running the example from the webbit github page. I added a bit more to the page to do some visualization with D3. I also added a PNG image to the page.
Now in Chrome the image is cut off after loading half of it and the D3 file does not load completely and therefore cusing a JavaScript error.
I thought this is a general webbit error, but loading the image using wget from the command-line works fine.
So now I'm rather confused.
Is there any known interaction between webbit and the browser, that produces this effect of corrupt responses?
Regards,
klaus