The popular NotFound handler for ASP.NET Core and Optimizely, enabling better control over your 404 page in addition to allowing redirects for old URLs that no longer works.
Apache License 2.0
19
stars
16
forks
source link
Misunderstanding / issues with 404 redirections #87
Hi,
We are having fundamental issues or misunderstandings in using the Not found Handler.
Two issues Ito document here…
ISSUE 1
We have old vanity links that no longer connect to their original media library URL in Optimizely. So they should be returning 404s.
Vanity URL
https://www.perpetual.com.au/PDF/QtrlySPF
We have also deleted any legacy of such a redirect in the handler (screenshot 1). And only have a redirect for the vanity URL pointing to the below rightful new home for the document…
We have tried setting up the redirect with and without our domain at the front https://www.perpetual.com.au/ with no success with either.
Could you please advise what we could do differently?
ISSUE 2
Perhaps connected to issue 1.
We have a number of the above URLs we need to change.
An example of one of those where it attempts to redirect to the right URL is for the vanity URL https://www.perpetual.com.au/PDF/QtrlyTGSO
I have attached (screenshot 2) the only redirect listed in the not found handler as a reference.
Could you please advise why this might be doing this?
Related Questions
From Geta’s perspective do we need to include the domain when we use the not found handler? i.e. https://www.perpetual.com.au/ (as it doesn’t seem to make a difference on our end).
Is there any difference or issue in having either URL in the handler with a file extension e.g .pdf and the other without .pdf?
Where if it all does capitalising URLs cause issues?
Hi, We are having fundamental issues or misunderstandings in using the Not found Handler. Two issues Ito document here…
ISSUE 1 We have old vanity links that no longer connect to their original media library URL in Optimizely. So they should be returning 404s. Vanity URL https://www.perpetual.com.au/PDF/QtrlySPF
Old media link no longer present in this media library structure https://www.perpetual.com.au/globalassets/_au-site-media/PDF/institutional/qtrlyspf.pdf
We have also deleted any legacy of such a redirect in the handler (screenshot 1). And only have a redirect for the vanity URL pointing to the below rightful new home for the document…
https://www.perpetual.com.au/globalassets/_au-site-media/01-documents/01-asset-management/01-fund-resources/fund-profiles/institutional/QtrlySPF.pdf
We have tried setting up the redirect with and without our domain at the front https://www.perpetual.com.au/ with no success with either.
Could you please advise what we could do differently?
ISSUE 2 Perhaps connected to issue 1. We have a number of the above URLs we need to change. An example of one of those where it attempts to redirect to the right URL is for the vanity URL https://www.perpetual.com.au/PDF/QtrlyTGSO
It wants to connect to the right URL structure but adds the unwanted anomaly: /PDF/%09/ https://www.perpetual.com.au/PDF/%09/globalassets/_au-site-media/01-documents/01-asset-management/01-fund-resources/fund-profiles/institutional/QtrlyTGSO.pdf
When it should simply be… https://www.perpetual.com.au/globalassets/_au-site-media/01-documents/01-asset-management/01-fund-resources/fund-profiles/institutional/QtrlyTGSO.pdf
I have attached (screenshot 2) the only redirect listed in the not found handler as a reference.
Could you please advise why this might be doing this?
Related Questions
Thanks