Johannes wrote:

I noticed two problems related to images:

Some websites seems to send images with a charset set in the header, e.g: Content-Type: image/jpeg;charset=ISO-8859-1 In that case dillo seems to decode the data resulting in: Not a JPEG file: starts with 0xc3 0xbf Not sure whether we can/want to do anything about that.

It seems like it would make sense to restrict decoding to text/*. I'll look in the rfc to see whether it says something relevant. It might be good to have text decoded outside of cache to UTF-8 in the same way that images are decoded outside of cache to RGB. (Right now that would be a problem with view src using getbuf, and perhaps for text/css following @charset="..." eventually, but still it would be nice to have one way of doing things.) Speaking of the rfc, I noticed just recently that it says "The value of Content-Location also defines the base URI for the entity." and I wonder whether that's ever a problem in practice because dillo makes no use of this header.

I don't understand the other problem: http://sz-magazin.sueddeutsche.de/upl/images/user/8059/17337.jpg loads and displays fine. from html however it doesn't work <img src="http://sz-magazin.sueddeutsche.de/upl/images/user/8059/17337.jpg" />

When you load it by itself, dillo follows the redirection to http://szmimg.sueddeutsche.de/upl/images/user/8059/17337.jpg