Opened 18 years ago

Closed 18 years ago

Last modified 18 years ago

#2476 closed enhancement (wontfix)

PREPEND_WWW setting in CommonMiddleware, but not REMOVE_WWW

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

Description

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@… 18 years ago.
Patch adding support for REMOVE_WWW

Download all attachments as: .zip

Change History (5)

by jeff@…, 18 years ago

Attachment: common-update.diff added

Patch adding support for REMOVE_WWW

comment:1 by Malcolm Tredinnick, 18 years ago

Resolution: invalid
Status: newclosed

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 no-www.org 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 by Malcolm Tredinnick, 18 years ago

Resolution: invalid
Status: closedreopened

comment:3 by Malcolm Tredinnick, 18 years ago

Resolution: wontfix
Status: reopenedclosed

comment:4 by jeff@…, 18 years ago

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 no-www.org before, also).

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