I thought that instead of redirecting with HTTP redirect codes (which requires the client to open a connection to the http server), a (sub-)domain redirect could be done instead on name-server basis (using CNAME), which would yield better performance results.
I would suggest adding a "CNAME" option to the redirect-code dropdown-list for (sub-)domains, but only if the redirect target is a host without special path requirements (as a CNAME entry would just "replace" the host in a URI, preserving the browser-requested path)
I was not sure I should open a new feature-request in redmine, so at first wanted to post here.
I would be able to implement the changes and push them to git, but would need some time first to look into the code.
Question
smat
Hello,
I thought that instead of redirecting with HTTP redirect codes (which requires the client to open a connection to the http server), a (sub-)domain redirect could be done instead on name-server basis (using CNAME), which would yield better performance results.
I would suggest adding a "CNAME" option to the redirect-code dropdown-list for (sub-)domains, but only if the redirect target is a host without special path requirements (as a CNAME entry would just "replace" the host in a URI, preserving the browser-requested path)
I was not sure I should open a new feature-request in redmine, so at first wanted to post here.
I would be able to implement the changes and push them to git, but would need some time first to look into the code.
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.