Django

Code

Ticket #8121 (closed: fixed)

Opened 4 months ago

Last modified 4 months ago

LocaleMiddleware should not set Content-Language header if already present

Reported by: jcassee Assigned to: nobody
Milestone: 1.0 Component: Internationalization
Version: SVN Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

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

8121-r8137.diff (0.6 kB) - added by jcassee on 08/05/08 10:02:52.

Change History

08/05/08 10:02:52 changed by jcassee

  • attachment 8121-r8137.diff added.

08/08/08 14:29:17 changed by ericholscher

  • needs_better_patch changed.
  • needs_docs changed.
  • stage changed from Unreviewed to Ready for checkin.
  • needs_tests changed.
  • milestone set to 1.0.

08/09/08 10:04:46 changed by mtredinnick

  • status changed from new to closed.
  • resolution set to fixed.

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

Add/Change #8121 (LocaleMiddleware should not set Content-Language header if already present)




Change Properties
Action