On 27 December 2012 17:18, Silvio Siefke <siefke_listen@web.de> wrote:
> Is Server or Script better?
Distinguishing between different versions of content that should be
served to different users for a single URI is the job of the
application, not the system underlying it.
Whilst there are cases where nginx (or "your HTTP server", as this
isn't an nginx-specific discussion) should do some of this work (e.g.
choosing between gzipped output or not), switching content based on
the user's desired language is absolutely not one of them.
There *are* nginx configuration options which look like they might
help you with this, like http://wiki.nginx.org/HttpSplitClientsModule.
Do not be fooled. They should *not* be used for something as complex
as language selection.
Read the 5 very informative posts here (read from bottom to top) for
much more information about the complexities that you'll face during
an internationalization process. Then imagine trying to solve those
problems just using an nginx config. Then realise that that's a daft
idea: http://codeascraft.etsy.com/category/internationalization/
Jonathan
--
Jonathan Matthews // Oxford, London, UK
http://www.jpluscplusm.com/contact.html
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
> Is Server or Script better?
Distinguishing between different versions of content that should be
served to different users for a single URI is the job of the
application, not the system underlying it.
Whilst there are cases where nginx (or "your HTTP server", as this
isn't an nginx-specific discussion) should do some of this work (e.g.
choosing between gzipped output or not), switching content based on
the user's desired language is absolutely not one of them.
There *are* nginx configuration options which look like they might
help you with this, like http://wiki.nginx.org/HttpSplitClientsModule.
Do not be fooled. They should *not* be used for something as complex
as language selection.
Read the 5 very informative posts here (read from bottom to top) for
much more information about the complexities that you'll face during
an internationalization process. Then imagine trying to solve those
problems just using an nginx config. Then realise that that's a daft
idea: http://codeascraft.etsy.com/category/internationalization/
Jonathan
--
Jonathan Matthews // Oxford, London, UK
http://www.jpluscplusm.com/contact.html
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx