Sinatra sends nonsensical charsets that can't be fully disabled #111

namelessjon opened this Issue Oct 30, 2010 · 2 comments

2 participants


The content_type helper function always adds a charset to the output.

It does this even with types that make no sense (e.g. image/png;charset=utf-8) and due to the implementation of the method, it's impossible to not send at least charset= if content_type is used, even if set :default_encoding, nil is used in addition to passing no charset along via the method params.

Sinatra member

Apart from this having to be fixed: Are there browsers that have issues with this?

Sinatra member

Only set default charset for specific mime type. Closed by aa06ed5.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment