"charset" ignored / not set for proxied content-type text/css resources

[Maxim Dounin]

Hello!

On Mon, Feb 08, 2010 at 11:05:56PM +0100, Daniel Hahler wrote:

> Maxim Dounin schrieb:
> 
> >> This works for application/x-javascript files (where "; charset=utf-8"
> >> gets added), but apparently gets ignored for "text/css" (which is not
> >> modified).
> >>
> >>         charset utf-8;
> 
> > As of now, by default charset module works only with the following 
> > types:
> > 
> > text/html
> > text/xml
> > text/plain
> > text/vnd.wap.wml
> > application/x-javascript
> > application/rss+xml
> > 
> > You may add more types via charset_types directive, see here (in 
> > Russian):
> > 
> > http://sysoev.ru/nginx/docs/http/ngx_http_charset_module.html#charset_types
> 
> Thank you, this worked fine.
> 
> I think text/html is fixed in this list, but all others must get added?
> (it says "[warn]: duplicate MIME type "text/html"" now).
> 
> This is probably like with gzip_types, where text/html is always being
> compressed / in the list.

Yes.

> > There is no translation of this directive description in wiki yet, 
> > feel free to add one.
> 
> I'd like to, but I don't understand a single word of the original
> documentation, which could lead to wrong information.. ;)

Google translate usally provides something readable, and someone 
with better knowledge will eventually clean it up. ;)

> I think it would make sense to add text/css to this list?!

Actually, it was removed from the list in 0.7.11.  Not sure why, 
most likely due to the fact that css isn't something that used to 
contain valuable non-ascii texts.

Maxim Dounin