You are reading a single comment by @Velocio and its replies.
Click here to read the full conversation.
-
I was looking through some HTTP traces trying to determine whether the measures I'd put in place with the browser caching strategy were working.
I have a fairly good eye for what the application should do, and was curious about the fact that the pagination links seemed to always trigger a 301 prior to returning the page.
Then I noticed this happened everywhere, but was so fast you wouldn't normally see it.
There may still be a few places left that are affected by this, specifically hard-coded URLs in templates. i.e. if a templates includes a link to
https://www.lfgss.com/search?type=eventrather thanhttps://www.lfgss.com/search/?type=eventthen a 301 will be fired.
Velocio
Did you find that through some form of automated bug checking? Or just something you noticed?
(just an interested question)