Add the active language to generate the cache key

a patch with the proposed cache key

aaloy: I don't think all keys should be affected by i18n. Perhaps there should be an alternate to the low-level cache that does add the active lang as a prefix?

This should probably only be done when USE_I18N == True, but otherwise this is a good idea.

This patch works against trunk and checks the USE_I18N setting. However, this patch is current blocked by #730. Incoming requests need to use the Session middleware, then Locale, then Cache, so that the language is determined by the time we hit the cache middleware. However, outgoing responses need Session before Cache as well so that the cookie-based Vary headers can be set.

Can someone please test attachment:middleware_ordering_with_path-weight_tuples-backwards-compatible.diff:ticket:730 ? Also see comment:26:ticket:730 .

Hrm, Django trac doesn't read links properly...

Patch: http://code.djangoproject.com/attachment/ticket/730/middleware_ordering_with_path-weight_tuples-backwards-compatible.diff Comment: http://code.djangoproject.com/ticket/730#comment:26

Note that this is viable again after [8260]. Patch probably still works, but I didn't like the duplication of code, and it still needs tests and docs of course.

I'm working on a patch which could work as:

    cache_key = 'views.decorators.cache.cache_header.%s.%s' % (
                      key_prefix, iri_to_uri(request.path))
    if settings.USE_I18N:
       cache_key += ".%s" % translation.get_language()

I have tested using other ways of string concatenations and this one is the fast way (0.6 s for 10^{6 interactions) for the kind of keys we're generating.}

cache pacth to use lang in the cache key

patch and tests for cache i18n key generation

Added the patch an the tests to check that we generate the right keys and that middleware recovers different content depending on the language.

/me wonders how the heck did my totally unrelated comments end up in this ticket!? My guess: nazi transgender aliens did it (it's still April 1 in my timezone, so don't you dare to disagree!).

Updated patch to port-r10335 and simplified tests

I've updated Antoni Aloy's patch to apply cleanly after r10335 and simplified tests to only include what's needed to run them as part of the Django test suite, also fixed them so they don't break other tests leaving test environment umodified.

Any progress on checking this in? This is looking good, isn't it?

update the patch against the latest trunk r12453

I'm not sure if we break a promise changing the cache key in 1.2 or if it's ok since _generate_cache_header_key is undocumented API anyway.

Anyway, a change needs to be documented.

jezdez in my oppinion this is not a new feature, is just a bug correction, as one may expect that on a multilingual content page the cache should depend also on the language. Anyway I would be glad to document it.

Please don't close the ticket if there wasn't an actual commit.

Opps. Sorry it was not my intention :(

Patch documentation

Added an updated patch with documentation warning about the new cache key generation. As is an internal feature I'm not really sure about if it has to be documented or not.

(In [12546]) Fixed #5691 - Adds the active language to the cache key. Thanks, Antoni Aloy, Ramiro Morales and Yann Malet.