Hi Arun, The response status for non-existing pages is 404, for both fastly and cloudflare.

Hi Arun,The error pages are published and rendered properly when requested individually. Also, I was checking the response headers for the existing and non-existing pages.It seems like the existing and non-existing pages are getting mapped properly at the fastly CDN ( x-cache being a fastly header)....

Hi Jagadeesh, I am trying to find the reason for /content/<name>/fr on top of the URL.But my main query is - the existing pages for FR are getting mapped properly with the same set of rules. Also, the response from the publisher is 404 and that is why the error page is getting mapped on publisher. 4...