13 messages in ru.sysoev.nginxRe: Content negotiation?| From | Sent On | Attachments |
|---|---|---|
| Nuno Magalhães | Jul 26, 2009 1:08 pm | |
| Igor Sysoev | Jul 26, 2009 11:19 pm | |
| Nuno Magalhães | Jul 27, 2009 4:39 am | |
| Nuno Magalhães | Jul 27, 2009 5:25 am | |
| Jeff Waugh | Jul 27, 2009 5:17 pm | |
| climbor | Jul 27, 2009 7:20 pm | |
| Igor Sysoev | Jul 28, 2009 12:01 am | |
| Jeff Waugh | Jul 28, 2009 12:37 am | |
| Nuno Magalhães | Jul 28, 2009 6:10 am | |
| Juan Fco. Giordana | Jul 29, 2009 1:15 am | |
| Maxim Dounin | Jul 29, 2009 4:01 am | |
| Nuno Magalhães | Jul 29, 2009 6:47 am | |
| Marcus Clyne | Jul 29, 2009 7:47 am |
| Subject: | Re: Content negotiation? | |
|---|---|---|
| From: | Igor Sysoev (is...@rambler-co.ru) | |
| Date: | Jul 28, 2009 12:01:53 am | |
| List: | ru.sysoev.nginx | |
On Tue, Jul 28, 2009 at 10:17:47AM +1000, Jeff Waugh wrote:
<quote who="Igor Sysoev">
nginx does not support content negotiation since I never saw working content negotiation setups, at least in Russia. Could you show good examples ?
One very simple but useful form of content negotiation is the ability to supply files according to the preferred mime types. For instance:
http://www.example.com/images/logo -> server provides logo.gif or logo.png depending on what the browser provides in the Accepts header.
I'm not sure that using content negotiation for images is good thing: all modern browsers understand basic mime types, and these images must be uncachable on transit proxies.
Then there's conneg for all kinds of other things like languages, but this might be a good first step for nginx.
The question is how many people set (or have by default) right language in browsers ?
-- Igor Sysoev http://sysoev.ru/en/