Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#2476 closed enhancement (wontfix)

PREPEND_WWW setting in CommonMiddleware, but not REMOVE_WWW

Reported by: jeff@… Owned by: adrian
Component: Tools Version: master
Severity: minor Keywords: www CommonMiddleware
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


In CommonMiddleware, there's a PREPEND_WWW setting, but not one for REMOVE_WWW, which is logical, since www is depreciated.

There's one available in URLMiddleware, or I've provided a patch which adds it to CommonMiddleware, as I think it should be.

Attachments (1)

common-update.diff (1.1 KB) - added by jeff@… 9 years ago.
Patch adding support for REMOVE_WWW

Download all attachments as: .zip

Change History (5)

Changed 9 years ago by jeff@…

Patch adding support for REMOVE_WWW

comment:1 Changed 9 years ago by mtredinnick

  • Resolution set to invalid
  • Status changed from new to closed

PREPEND_WWW exists to provide a way to create uniform URLs. Adding another setting that does the same thing in a slightly different way is just adding to the settings for no real technical reason. If somebody *really* want to remove www always, they can write their own middleware or use web server rewriting.

The www subdomains are not in any way deprecated, despite what might want people to believe, so there is no strong reason to prefer www-stripping to www-adding as far as uniformisation goes.

comment:2 Changed 9 years ago by mtredinnick

  • Resolution invalid deleted
  • Status changed from closed to reopened

comment:3 Changed 9 years ago by mtredinnick

  • Resolution set to wontfix
  • Status changed from reopened to closed

comment:4 Changed 9 years ago by jeff@…

Alright, the people in the IRC room immediately yelled that www was depreciated, as soon as I mentioned this. So, I took their word for it (plus, I had seen before, also).

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