Content-Type with charset
mat999 at gmail.com
Tue Oct 26 12:10:52 MSD 2010
Ive seen other applications drop the quotes too maybe nginx should be less
On Tue, Oct 26, 2010 at 7:01 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:
> On Mon, Oct 25, 2010 at 05:31:35PM -0700, Matthieu Tourne wrote:
> > Hello,
> > I have a case where the origin server behind nginx returns this header:
> > Which seems to be valid according for HTTP/1.0  and HTTP/1.1  rfcs.
> This doesn't looks valid. Valid one will look like
> Parameters should be in form 'attribute "=" value, see here:
> > part seems to throw off ngx_http_test_content_type()
> > This simple patch included below seems to fix it, but it's not exactly
> > production ready.
> > Is there another way to make this work ?
> Valid charset specifications should work as is. Other parameters
> will confuse content type testing, but this isn't believed to be
> widely used.
> Maxim Dounin
> nginx mailing list
> nginx at nginx.org
Warez Scene <http://thewarezscene.org> Free Rapidshare
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx