2011/3/4 Mikołaj S. <[email protected]>: > I know, but it just seems so obvious to me that I can't believe no one have > ever encountered this problem before - I felt like I should ask ;) > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. >
Here are some tickets you might find interesting: http://code.djangoproject.com/ticket/13217 http://code.djangoproject.com/ticket/12794 http://code.djangoproject.com/ticket/65 If you disable sessions, django will use a cookie to store the language. If you have sessions enabled, then django checks the session first which results in adding "Vary: Cookie" (even if it doesn't contain any info). I'm not an expert on caching, but even if you add a seperate cookie for a language, but keep the sessions framework enabled, wouldn't that still break caching ? After all the (session, language) cookie pair is still unique and the "Vary" header doesn't let you name specific cookies, AFAIK. -- Łukasz Rekucki -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
