Giving a route name an extension

Personally I wouldn't do that. I would set up redirects. I am not 100% sure on how to hook into Laravels system for this but just before a 404 page loaded there might be a way to set up a look up table (a db table with old url --> new url) and redirect to the new url with a 301 redirect

I created a file called podcast_rss.php that was a 301 redirect and itunes coughed up a lung. Gave a 301 error.

The current solution makes me feel very dirty. I duplicated the index.php file and renamed it podcast_rss.php

then I created a filter that checks the basename of the URL. If it's podcast_rss.php it runs the same code the feed controller does. But I cut and pasted.

Oh Lord forgive me I cut and I pasted.

Definitely wouldn't be doing that.

I am not certain how Laravel handles .php extensions I just get a no input specified page (I think it's just telling you it cannot find a page to execute). But for these things it's redirects you want. You need to be telling search engines that the page has moved, not giving it 2 of the same page and users would just get redirected to the correct url

Just found this, this may help you https://laracasts.com/discuss/channels/requests/nginx-on-homestead-error-while-visiting-urls-that-end-with-php-extension?page=1

.php in route does work but I wouldn't recommend it. Can easily do a 301 redirect with Nginx or Apache.

I had already set up a 301 redirect using php header codes. Turns out iTunes didn't like that. Now that I've set it up with Nginx it's all working like a charm. Thanks.

Always best to do it in the web server config indeed :)