Opened 10 years ago

Closed 10 years ago

Last modified 7 years ago

#8121 closed (fixed)

LocaleMiddleware should not set Content-Language header if already present

Reported by: Joost Cassee Owned by: nobody
Component: Internationalization Version: master
Severity: Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


The user may have added the Content-Language header to the Response objects explicitely. In that case LocaleMiddleware should not overwrite it. Attached patch fixes this.

Attachments (1)

8121-r8137.diff (575 bytes) - added by Joost Cassee 10 years ago.

Download all attachments as: .zip

Change History (4)

Changed 10 years ago by Joost Cassee

Attachment: 8121-r8137.diff added

comment:1 Changed 10 years ago by Eric Holscher

milestone: 1.0
Triage Stage: UnreviewedReady for checkin

comment:2 Changed 10 years ago by Malcolm Tredinnick

Resolution: fixed
Status: newclosed

(In [8259]) Fixed #8121 -- Don't override the Content-Language HTTP header in the locale
middleware if it's already been set. Thanks, jcassee.

comment:3 Changed 7 years ago by Jacob

milestone: 1.0

Milestone 1.0 deleted

Note: See TracTickets for help on using tickets.
Back to Top