Feature #50319
closed
Added by Ralle Büchnitz over 11 years ago.
Updated almost 10 years ago.
Description
Domain handling could be improved and simplified by some more options like:
Right now you need to add at least two domain records. One for redirecting to the desired domain with or without 'www' and then the needed domain-record with your domain as string. I think every admin would do this due to duplicate content issues.
p.e.:
- typo3.org --> www.typo3.org (Redirect 301)
- www.typo3.org
If you add these two doamin-records now you need to be aware of the order inside the root page, don't you? And you need to test whether you need to add
http://-prefix to a field or not. I usually test the behaviour by right clicking on the page-tree and open a new browser tab with the desired page. But this fails quite often because the generated link is something like this
I would therefore change the mask as you can see in the attached picture.
- let the user decide whether to prefer www or not
- let the user decide whether to prefer https or http
- add a subdomain field to cover full subdomain support
- js-validate the domain (blank without www and http and so on) (absRefPrefix should go to another field)
- implement the redirection rules (first: http or https and thenn www or not)
- typo3 should build the final domain-string by stripping stuff and rearranging
Files
- Category set to Miscellaneous
- Status changed from New to Accepted
- Priority changed from Should have to Could have
- % Done changed from 0 to 50
- Complexity set to medium
www.example.com and example.com are completly distict domains with no relation to each other. I suggest to not add magic like this as this heavily depends on the server settings.
A domain does not have a protocol as this is not important for domains. The distinction between protocols is done on page level.
We could think of automatically sanitizing any protocol away from the domain, but this should go into a new issue.
For subdomains, you should checkout this change request:
https://review.typo3.org/#/c/9263/
- Status changed from Accepted to Needs Feedback
I think that the current handling of domains could be done easier.
So that was just my first approach how to solve it. And in this particular case from a user-perspective.
I do know that the www-subdomain is not logically connected to the tld. But people are used to it. And I think many domains perform a redirect to avoid duplicate content on search engines either from www.whatever.com to whatever.com or the other way round.
(I don't know a site where www.whatever.com has other content than whatever.com.)
Right now you have full control of domain handling.
Maybe the 'www-subdomain'-section should be allowed to be deactivated/activated. But I think the user-interface is getting to complicated?!
What do you think?
Such redirect should be done on webserver level (or .htaccess).
IMHO such a feature would make the code more complicated and error prone without much benefit for most installations. Also this would be too much magic.
As Philipp wrote, this should go in the .htaccess or server configuration. No need to start a TYPO3 instance, get records from a database to only redirect a user to another domain.
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Taken into account in #64674.
The issues are not linked on purpose, so the refactoring ticket does not get bloated with relations.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 