tao
commented
3 years ago Sorry to drop into the conversation, but I thought I would add something and see if it could help clarify this issue because I think I have the opposite problem?
If I use Statamic with php artisan serve there are no trailing slashes and everything works fine. If I manually add a slash to the url it still works.
When I use SSG and generate a site, I run a small PHP web server to test the site with php -S localhost:9000 and there are no trailing slashes in the URLs and it works exactly the same as the dynamic site when using php artisan serve or Laravel Valet. When I manually add a slash to the end of the url it still works.
When I deploy the site to AWS CloudFront, it works normally when the url doesn't have a slash but when someone visits the website and puts a slash at the end of the url (by mistake) then I have to manually add an index.html with a Lambda function on every request or it breaks.
Something like this for example:
exports.handler = (event, context, callback) => {
let newUri;
let requestUrl = request.uri;
// test url and skip assets with .jpg, .png, etc...
// Match any '/' that occurs at the end of a URI. Replace it with a default index
if (requestUrl === '/index.html') {
// handle root url
newUri = '/index.html';
} else {
// handle sub pages
newUri = requestUrl.replace(/\/+$/, '') + '/index.html';
}
// Replace the received URI with the URI that includes the index page
request.uri = newuri;
// Return to CloudFront
return callback(null, request);
}So in all these cases it seems the default from webservers is no trailing slash, and when there is a trailing slash it breaks my site on CloudFront...
fitzage
kyranb
jasonvarga
nickebdon
RussBrown00
el-schneider
RiaanZA
architchandra
anardil
When running statamic dynamically, URLs get standardized to no trailing slash. However, when the SSG generates a site, every page is a directory, and webservers treat them this way. Since I'm not running an apache server where I can just add a fancy htaccess rule, all my page URLs have trailing slashes.
This isn't a big deal, except that in some deployments, I now end up with every URL that doesn't have a trailing slash getting redirected to the trailing slash. This is also not generally a big deal, but now my sitemap.xml, rss feeds, and nav links don't match up with the actual URLs.
This is also apparently not a big deal in general, until you get to my third part search tool (addsearch). I'm working with them to hopefully fix the issue their bot has with the 308 redirects that my static site hosting platform (CloudFlare Pages) implements for their URL normalization (and no, I don't have enough details to know all the pieces).
This appears like it would be resolved if the URLs discovered in my nav tags, and in my sitemap, and in my RSS feeds all had a trailing slash.
I could manually "fix" some of them, but not the sitemap generated by SEO Pro. It seems this might be a useful default (or just an option) for the SSG to handle when generating permalinks and urls.