Randy, I want to thank you a lot, your answers are really helping me 😊
While I try to wrap my brain around your other “I’m not designing around the URI scheme” questions, let me work on this one…You are right, I didn’t understand this at first. I think that is because I’m attempting to see this from the pragmatic view point of the user.
What do you expect to do if, under the the certain circumstance, the use DOES type in “index.php” on the address bar? Send a jolt of lightning through the ether and kill them on the spot? 😏
The short answer is it only affects generated URLs.
—-I’m just having some fun. I’m looking at the other questions too.
LOL 😛
Great, thanks. 😊
What I was expecting was either a 404 error or a redirect, or that it only affected generated URLs (in fact, I was pretty sure it only affected generated URLs). I just figured that if there was an easy way to invalidate those extra URLs, I would do it.
I’m perplexed by this question because you ask specifically about canonicalization but then follow with two URLs that don’t touch on the www vs. non-www hot button issue. So I truly don’t understand the question. The routing class will allow you to do almost anything like this as you’ve already rebuked me about. So what exactly are you asking?
That’s the answer I was looking for. 😊
I thought routing only took care of mapping URLs to controllers though. Or do you mean I should have my own subclass of Router that also handles redirects like this?
And the reason I didn’t ask about www versus non-www is because I do see that as more of a webserver configuration issue. It can be handled at the application level, but it seems to me that it should either be done via DNS or via the webserver, since a domain can contain more than one application.