Redirect Issues

[colinvlasak]

Some of the redirects that are logged in the Redirect sheet are not working. They are in the sheet but they don't redirect on the live site.

I think this may be a result of them having special characters. These were legacy urls. How do we see that they redirected?

Examples

<style> </style>

Original URL	Proposed Destination	Action
https://www.shredit.com/en-us/blog/identity-protection/7-ways-identity-thieves-steal-personal-id-–-and-ho	https://www.shredit.com/en-us/blog	301 Redirect URLs in column C to Final URL in column D
https://www.shredit.com/en-us/blog/securing-your-information/july-2016/office-security-focus-on-employees,-not-just-digi	https://www.shredit.com/en-us/blog/what-types-of-documents-should-i-shred	301 Redirect URLs in column C to Final URL in column D
https://www.shredit.com/en-us/blog/securing-your-information/august-2017/7-ways-identity-thieves-steal-personal-id-�-and-ho	https://www.shredit.com/en-us/blog/effective-strategies-for-enhancing-workplace-data-security	301 Redirect URLs in column C to Final URL in column D
https://www.shredit.com/en-us/blog/securing-your-information/march-2016/how-to-set-a-document-management-policy-in-stone-�	https://www.shredit.com/en-us/blog/how-to-make-a-security-risk-assessment-work	301 Redirect URLs in column C to Final URL in column D
https://www.shredit.com/en-us/blog/securing-your-information/march-2016/how-to-set-a-document-management-policy-in-stone-–	https://www.shredit.com/en-us/blog/how-to-make-a-security-risk-assessment-work	301 Redirect URLs in column C to Final URL in column D
https://www.shredit.com/en-us/blog/securing-your-information/november-2017/7-common-data-security-mistakes-–-and-how-to-corre	https://www.shredit.com/en-us/blog/how-to-make-a-security-risk-assessment-work	301 Redirect URLs in column C to Final URL in column D
https://www.shredit.com/en-us/resource-center/newsletters	https://www.shredit.com/en-us/blog/effective-strategies-for-enhancing-workplace-data-security	301 Redirect URLs in column C to Final URL in column D

[colinvlasak]

@MarquiseRosier @kronnox can you take a look at this?

[kronnox]

I think it's due to the special characters and patterns in the URLs. I know only specific characters are accepted here, but there should be changes that can be applied to the CDN to fix this. I'll reach out to some folks and see if we can get this resolved.

[kronnox]

For reference:

The currently allowed set for an incoming request target path is [/a-zA-Z0-9._-] excluding any path matching ".." or "/./" or "//".

[colinvlasak]

@kronnox thanks for the update. Keep me posted on a solution to resolve this.

[ericvangeem]

This can be handled by the Fastly CDN, assigning this ticket to the HD team.

[rene-davila-hero]

@colinvlasak There seems to be a couple of inconsistencies between the destination urls on the spreadsheet and the ones you posted here, which one should I use?

[colinvlasak]

@rene-davila-hero please use what's listed here. I made one update to the first one which is now reflected in the chart (I changed the destination to https://www.shredit.com/en-us/blog)

[rene-davila-hero]

@colinvlasak We have deployed the fix to stage. You can test by changing the "www" on the URL to "stage-us". For example https://stage-us.shredit.com/en-us/blog/securing-your-information/august-2017/7-ways-identity-thieves-steal-personal-id-%C2%96-and-ho

[colinvlasak]

@rene-davila-hero looks good for most there are two which are still resulting in a 404:

https://stage-us.shredit.com/en-us/blog/securing-your-information/august-2017/7-ways-identity-thieves-steal-personal-id-%EF%BF%BD-and-ho

https://stage-us.shredit.com/en-us/blog/securing-your-information/march-2016/how-to-set-a-document-management-policy-in-stone-%EF%BF%BD

[rene-davila-hero]

@colinvlasak I added the redirects for the urls above, I assumed the destination is the same as on the description. Could you please validate? Also, there is an issue on the author environments for the EMEA sites that needs a CDN configuration fix, Is it ok with you if I deploy to production that fix along these redirects, after validation?

[colinvlasak]

@rene-davila-hero looks good. Yes if you can roll out the fix for these redirects and the fix for the AEM authoring as soon as possible that would be great. That AEM authoring issue is a global problem