It seems there's an issue with the WAF configuration in your Cloudflare setup, which is preventing access to any requests that include query parameters. Implementing such a rule might not be the best approach for several reasons.
Firstly, this configuration could inadvertently block access to many static assets, which often rely on query parameters.
Secondly, it might also filter out legitimate requests originating from platforms like social media.
To enhance the functionality and accessibility of your website, consider the following adjustments:
Make an exception for all static asset paths from this rule to ensure they are not blocked, or simply move them to a CDN.
Rethink the strategy of using a 403 error code for blocked requests. A more user-friendly approach might be to redirect users to your website's homepage or to the original path they were attempting to access. Additionally, you could configure rules to overlook query parameters concerning caching. This would allow for effective caching without the need for redirections or displaying a 403 error.
It seems there's an issue with the WAF configuration in your Cloudflare setup, which is preventing access to any requests that include query parameters. Implementing such a rule might not be the best approach for several reasons.
To enhance the functionality and accessibility of your website, consider the following adjustments:
Make an exception for all static asset paths from this rule to ensure they are not blocked, or simply move them to a CDN.
Rethink the strategy of using a 403 error code for blocked requests. A more user-friendly approach might be to redirect users to your website's homepage or to the original path they were attempting to access. Additionally, you could configure rules to overlook query parameters concerning caching. This would allow for effective caching without the need for redirections or displaying a 403 error.