Trailing slash support moved
Created: Last updated:
A trailing slash in an URL was not really a problem for the application but it lead to duplicate content in search engines. See my take on Trailing slashes for SEO.
The framework originally ignored the slash and simply returned the same page. Google, for reasons I could not figure out, suddenly attempted to request pages with trailing slashes and of course indexed both versions. A fix has been introduced a couple months that returns a 301 redirect response instead of the webpage.
The original fix was a little late in the process which is not only bad because it takes longer but I did not include modules unless they extended to the main model.
I have moved the fix ahead in the process which (a) speeds up the process and (b) includes all pages including modules.