XF 2.3 Why are some template names all caps?

josh_b_and_b

New member
Why are some templates like "PAGE_CONTAINER" in all caps in upper case while others are not?

I'm getting a 403 when editing any template that has a name that's all caps. I tried editing the DB directly but that had no effect so I'm going to have to dive into why only a very small subset of templates give 403s.

First order of business is figuring out what's different about the caps vs all the other templates.

1728676400788.webp
 
Templates with capitalized names are the final page (container) templates, eg. those that open and close <html>

All other templates are just parts used somewhere within the container.

If you get 403s for some templates it's most likely a server configuration issue like ModSecurity or CloudFlare WAF.
 
Templates with capitalized names are the final page (container) templates, eg. those that open and close <html>

All other templates are just parts used somewhere within the container.

If you get 403s for some templates it's most likely a server configuration issue like ModSecurity or CloudFlare WAF.
Interesting. I'll keep digging. I have no WAF rules and CF security is set to "essentially off".

Found my 403 in CF and says "not mitigated" as well so I think that rules out CF.

1728682308045.webp

Just disabled ModSecurity and still same 403. I'm going to keep digging.

1728682980163.webp
 
Probably something to do with it containing a <script> tag as it's detected as an XSS injection. If you inspect the request in developer tools the response will likely be a Cloudflare page, or some sort of error page that should flag why it's blocked.
 
Found my 403 in CF and says "not mitigated" as well so I think that rules out CF.
Nope, the oppositie is true:
Your screenshot pretty much proves that the source is CF as the origin status code is none, eg. the request never reached the origin server.

Check the CF managed WAF rules.
 
Last edited:
Back
Top Bottom