easymode.middleware

Google Analytics

Easymode has middleware to support caching in combination with google analytics. Google analytics updates a session cookie on each request. Because django’s SessionMiddleware places cookie in it’s vary header, you will save every single request to the cache if you use it.

class easymode.middleware.NoVaryOnCookieSessionMiddleWare

Works like django’s django.middleware.SessionMiddleWare, but it does not add cookie to the vary header. You need this if you use google analytics and want to use django site caching.

Internationalization related middleware

When using the internationalization middlewares, you should include easymode.urls in your url conf:

(r'^', include('easymode.urls')),

This will make sure that when you have defined get_abolute_url on your model, the view on site button will lead you to the page in the language you have currently selected.

class easymode.middleware.LocaleFromUrlMiddleWare

Like django.middleware.LocaleMiddleware this middleware activates the current language. It does not try to guess the language from the request headers, it looks for it in the url, or it defaults to settings.LANGUAGE_CODE.

Also we don’t use the accept language to determine the language of the page anymore, so the Accept-Language is nolonger considered for the vary headers.

class easymode.middleware.LocaliseUrlsMiddleware

This middleware replaces all anchor tags with localised versions, ugly but it works.

Don’t put any vary header for the Accept-Language because the language does not depend on the vary header, the language is in the url.

class easymode.middleware.ShortLocaleFromUrlMiddleWare

deprecated, LocaleFromUrlMiddleWare does exactly the same, if you’ve set USE_SHORT_LANGUAGE_CODES to True.

class easymode.middleware.ShortLocaleLocaliseUrlsMiddleware

deprecated, LocaliseUrlsMiddleware does exactly the same, if you’ve set USE_SHORT_LANGUAGE_CODES to True.