#24983 closed Cleanup/optimization (fixed)
"domain" in sites framework should clarify if it is a fully-qualified domain name
Reported by: | mandm | Owned by: | bipsandbytes |
---|---|---|---|
Component: | Documentation | Version: | 1.8 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
The documents on sites framework should clarify that the domain should be a "fully qualified domain name" or just the "domain name".
An example where things can be confusing:
I have a setup where all requests to non-www domain i.e. http://example.com
are redirected (with status 301) to http://www.example.com
by the webserver. Hence I've set my preferred site in google webmasters tool as www.example.com
(as opposed to example.com
). When I use the sitemap framework, the urls generated are http://example.com/abc
which is incorrect in my case. This makes me think that the domain in sites framework should have been www.example.com
(instead of example.com
). This is not evident from the documentation.
Change History (6)
comment:1 by , 9 years ago
Easy pickings: | set |
---|---|
Triage Stage: | Unreviewed → Accepted |
comment:2 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Yes, I believe it should be fully-qualified. On djangoproject.com, for example, we have the domains docs.djangoproject.com and www.djangoproject.com.