Code

Changes between Version 34 and Version 35 of ContributedMiddleware


Ignore:
Timestamp:
06/07/07 07:14:10 (7 years ago)
Author:
anonymous
Comment:

Being in web development for a long time this is the first time that I heard that embedding the language in the url is supposed to be bad practice. Contrary to that opinion most international users find it very intuitive and good to have the language in the url. Maybe elaborate with some sources? Either way I don't believe this page is the right forum for a subjective comment like that or for a discussion about it.

Legend:

Unmodified
Added
Removed
Modified
  • ContributedMiddleware

    v34 v35  
    99For example /fr/article/... shows you the article in French, and /en/article/... shows it in English. 
    1010This version of the Locale from URL Middleware also sets a cookie and a request var whenever you go to a webpage that has a language set in it's url, so that it serves you the correct version when you go to a page that doesn't have any language code in it's url. 
    11  
    12 "This middleware goes against many principles of good URI design. Document language should be a specified in the HTTP request headers (and optionally as a query string parameter) and served using content negotiation. Embedding language information in a URI is considered bad practice." - Noah Slater 
    1311 
    1412=== [http://www.rhonabwy.com/wp/2006/08/01/blocking-a-site-in-django/ BlockingMiddleware] by Joe Heck ===