Hopbot log for 2009-07-09 - Helma IRC channel: #helma on irc.freenode.net

2009-07-09:

[10:07] <kstrieder> hi all
[10:08] <kstrieder> in helma 1.6.3 -- res.contentType = "image/png"; produces this http header: Content-Type: image/png; charset=ISO-8859-1
[10:09] <kstrieder> I suppose that charset is not correct with image-mimetypes.
[10:09] <kstrieder> how can I get rid of it?
[10:15] <simono> kstrieder, don't know how to get rid of it.. but does it matter?
[10:16] <kstrieder> I get different byte-results with different charsets when testing with w3m. So at least this client interprets it. UTF8 would be a destructive charset, as not all byte-values are valid.
[10:16] <simono> what's w3m?
[10:17] <simono> when sending binary data image/png the charset shouldn't matter
[10:19] <kstrieder> w3m is a command-line http-getter. I always used it as a reference-test
[10:19] <kstrieder> the bytes differ:
[10:19] <kstrieder> Content-Length: 10788
[10:19] <kstrieder> Content-Type: image/png; charset=UTF8
[10:19] <kstrieder> -rw-r--r-- 1 ska ska 10671 2009-07-09 12:25 byteresult
[10:19] <kstrieder> Content-Length: 10788
[10:19] <kstrieder> Content-Type: image/png; charset=ISO-8859-1
[10:19] <kstrieder> -rw-r--r-- 1 ska ska 10687 2009-07-09 12:25 byteresult
[10:22] <simono> you can set the responsecharset with res.charset http://helma.server-side-javascript.org/reference/res.html
[10:23] <kstrieder> I know, but I want to kill the subheader for binary-results. I used res.charset for the example above.
[10:23] <simono> i would check the RFC if charset matters at all for binary content-types.. i would guess it does not
[10:25] <kstrieder> charset is only mentioned for text/ types. One could deduct, that other mime-types should not have charset or that it should be ignored. anyway, at least one client behaves differently.
[10:25] <kstrieder> but some helma-installations behave correct - I want to too:
[10:25] <kstrieder> Content-Type: image/png
[10:25] <kstrieder> Content-Length: 17740
[10:26] <kstrieder> http://helma.zumbrunn.com/static/helmaheader.png
[10:26] <kstrieder> ;-)
[10:26] <kstrieder> Suppose that's just jetty alone setting the mimetype.
[10:27] <kstrieder> btw. helma.Image.spacer() also has charset set.
[10:27] <simono> maybe zumbrunn knows how to do that then :)
[10:29] <simono> can you check what difference it makes in w3m? if it really modifies the binary data somehow depending on the charset, then i would say that's a bug
[10:30] <kstrieder> could be a bug in w3m, I'll check against wget.
[10:32] <kstrieder> wget always produces the same result, byte-identical.
[10:32] <simono> hm, good :)
[10:32] <kstrieder> I'ld prefer not give buggy clients a chance. I expected it easier to fix on my side than on others.

 

 

In the channel now:

Logs by date: