localize using querystring vs cookie [Answered]RSS

• • Reply
  Peter Smith

  Member

  613 Points

  2132 Posts

  localize using querystring vs cookie

  Dec 18, 2007 12:44 PM|Peter Smith|LINK

  Could someone provide an overview what the pros and cons are of localizing via the querystring or via a cookie?
  
  querystring: www.mysite.com/?lang=en
  or
  cookie: www.mysite.com where I read the language from a cookie.
  
  AND, not sure if it matters: I use dynamic subdomains:
  
  so username.mysite.com is a valid address (I've heard that this might be an issue when using cookies...)
  
  Thanks!
  

  please mark answers as 'Answered' and post back solutions when you figure stuff out that isnt in the post already.
• • Reply
  anas

  All-Star

  69062 Points

  7992 Posts

  Moderator

  Re: localize using querystring vs cookie

  Dec 18, 2007 05:29 PM|anas|LINK

  i would recommended to use the QueryString for that ,

  this will make it easy to implement OutputCaching per language for every page.

   

   

  Anas Ghanem
  
• • Reply
  vivek_iit

  Star

  9003 Points

  3165 Posts

  Re: localize using querystring vs cookie

  Dec 20, 2007 02:49 PM|vivek_iit|LINK

  I would recommend using QueryString as it has benefits like:

  1. Even if user browser has cookies disabled, it will work.

  2.  No issues with dynamic subdomains.

   

  Cons:

  1. "bad looking" URL with "?" sign

  2. some search engines (not google) do not index pages with "?" in the URLs.

  You can avoid these cons by using a URL rewiter (get one free rewriter here:  http://urlrewriter.net) 

  Hope this helps,

  Vivek 

  CodeASP.NET Community
  
  Communifire: Social Networking and Business Collaboration Platform