Today, we had our website start failing in places were we were redirecting to a page using relative pathing. In the past, we would redirect to a relative path like /us-en and it would basically be going to the same page as mydomain.com/us-en and work just fine. We could go directly to mydomain.com/us-en and it would work just fine. It was only when redirecting in code to the relative path that it would get the extra / and give a 404 error.
This morning, that broke and it took us forever to find out what was happening, and essentially with no code changes in five weeks (this part of the site, possibly not for a year or so), now was redirecting to //us-en which was failing, because Apache was no longer seeing it as a relative path, but instead an absolute path (at least that's our theory).
Does anyone know of a upcp update last night (on release 11.44.1.23) that would have caused this problem to occur?
This morning, that broke and it took us forever to find out what was happening, and essentially with no code changes in five weeks (this part of the site, possibly not for a year or so), now was redirecting to //us-en which was failing, because Apache was no longer seeing it as a relative path, but instead an absolute path (at least that's our theory).
Does anyone know of a upcp update last night (on release 11.44.1.23) that would have caused this problem to occur?
