Production DNS is configured entirely in Cloudflare.
Development Sitemap.xml file loads without issue, and is clearly visible and formatted correctly.
Production Sitemap.xml file will not loaded at all, the page just freezes up.
I’ve tried debugging both Development and Production versions of the Sitemap.xml file, and there isn’t an issue with the formatting at all, however, the Production version of the Sitemap will not load and I’m wondering whether this is being blocked by Cloudflare (assumption based on the fact that the only difference between the 2 versions are that Production is running in Cloudflare, and Development isn’t).
Generally, yes. That is what I was referring to. You can expand the entries to view more detail. You would want to check for any entries that show your sitemap.xml was blocked and review the reason. You can then make adjustments to avoid the block.
Looking at output from testing with curl it becomes apparent that this is not the WAF, but a 502 error on your origin.
I don’t why your server is having trouble with that file when it is requested via the Cloudflare proxy. While it loaded for me during a couple of attempts via web browser, the page acted like it was still loading even after the sitemap had loaded. My final attempt ended in the fancy Error 502 page served by Cloudflare when it is sent a 502 response from the origin.
If you have access to your server logs, you might want to examine them as well to see if it is logging any errors when the sitemap.xml file is requested via Cloudflare proxy.
