Cloudflare issue. Is this a bug

[alani123]

When I click the 'all' link on a thread, I get the cloudflare message and I'm then re-directed to the homepage. Usually this won't happen again in the same session but it's still annoying.

I assume the forum is doing this to check on users that request too much data in once instance, but if the test is completed why not land the user in the page he was intended to visit?

[1715000644]

1715000644

[1715000644]

1715000644

[SFR10]

When I click the 'all' link on a thread, I get the cloudflare message and I'm then re-directed to the homepage.

I tried to replicate it but it always lands on the right page (no redirection whatsoever). Perhaps it has something to do with your browser's configuration (have you tried replicating the situation on other browsers?)...
- Tested on Chrome, I.E, Firefox and Edge.

[blackssmith2018]

When I click the 'all' link on a thread, I get the cloudflare message and I'm then re-directed to the homepage. Usually this won't happen again in the same session but it's still annoying.

I assume the forum is doing this to check on users that request too much data in once instance, but if the test is completed why not land the user in the page he was intended to visit?

We are the same issue but I already fix it I clear all my history in chrome cookies password etc. and update my chrome browser then try to flush your dns by doing in command prompt ipconfig/flushdns. It's work's on me

[Foxpup]

It redirects based on your HTTP Referrer header. If your browser doesn't send one (usually because you're using a privacy-enhancing plugin that blocks it), you get dumped onto the home page. All Cloudflare redirects work this way because they haven't figured out that the best way to send the redirection target is as a query parameter.

[alani123]

It redirects based on your HTTP Referrer header. If your browser doesn't send one (usually because you're using a privacy-enhancing plugin that blocks it), you get dumped onto the home page. All Cloudflare redirects work this way because they haven't figured out that the best way to send the redirection target is as a query parameter.

Seems like that could be it more likely than not. Thanks.