Middleware ordering

Table 17.1 provides some hints about the ordering of various Django middleware classes:

Class	Notes
UpdateCacheMiddleware	Before those that modify the Vary header (SessionMiddleware, GZipMiddleware, LocaleMiddleware).
GZipMiddleware	Before any middleware that may change or use the response body. After UpdateCacheMiddleware: Modifies Vary header.
ConditionalGetMiddleware	Before CommonMiddleware: uses its Etag header when USE_ETAGS = True.
SessionMiddleware	After UpdateCacheMiddleware: Modifies Vary header.
LocaleMiddleware	One of the topmost, after SessionMiddleware (uses session data) and CacheMiddleware (modifies Vary header).
CommonMiddleware	Before any middleware that may change the response (it calculates ETags). After GZipMiddleware so it won't calculate an ETag header on gzipped contents. Close to the top: it redirects when APPEND_SLASH or PREPEND_WWW are set to True.
CsrfViewMiddleware	Before any view middleware that assumes that CSRF attacks...