Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#27041 closed Cleanup/optimization (fixed)

Note that middleware included with Django is compatible with both MIDDLEWARE and MIDDLEWARE_CLASSES

Reported by: Ville Skyttä Owned by: nobody
Component: Documentation Version: 1.10
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I could not find a note in the docs that would say that all middleware included with Django is compatible with both MIDDLEWARE and MIDDLEWARE_CLASSES. This is useful information to have in case one is migrating to 1.10 but has some middleware which has not yet been migrated to the new style.

Change History (4)

comment:2 by Tim Graham <timograham@…>, 8 years ago

Resolution: → fixed
Status: new → closed

In 630613d7:

[1.10.x] Fixed #27041 -- Documented that built-in middleware are compatible with MIDDLEWARE and MIDDLEWARE_CLASSES.

Backport of f95bd89e827d6ee46cc6c736dadc25a10ae25fc9 from master

comment:3 by Tim Graham <timograham@…>, 8 years ago

In f95bd89e:

Fixed #27041 -- Documented that built-in middleware are compatible with MIDDLEWARE and MIDDLEWARE_CLASSES.

comment:4 by Tim Graham, 8 years ago

Type: Uncategorized → Cleanup/optimization
Note: See TracTickets for help on using tickets.
Back to Top