If this would not be tragicomic, then I'd say it's a recursive bug...
Just posted this: https://forums.garmin.com/developer/connect-iq/f/forum-about-the-forum/408714/tags-pages-are-unaccessible
But that link is also unaccessible:
If this would not be tragicomic, then I'd say it's a recursive bug...
Just posted this: https://forums.garmin.com/developer/connect-iq/f/forum-about-the-forum/408714/tags-pages-are-unaccessible
But that link is also unaccessible:
EDIT: deleted a bunch of incorrect speculation about why your posts were blocked (I thought it might've been because you post the tag links themselves, but ofc that makes little sense since any topic is able to have that kind of link)
It turns out that any forum page with "/tags" in the url is blocked by cloudflare
Test post:
Huh that's weird, I can't imagine what was in your post (actually 2 posts) which got them blocked.
Could it literally be the words "tags"?
Aha, if the first word of your topic title is "tags" then it creates a url including "/tags" which cloudflare won't allow you to visit.
My post entitled "test post about tags" is fine, but "tags test post" is blocked.
All of the "tag links" also include "/tags", so the bug is perfectly consistent. It's not actually recursive at all, although it kinda seems that way, as certain attempts to talk the bug will also trigger it haha.
Any forum url containing "/tags" will return a cloudflare error page.
> forum unaccessible
speaking of bug report titles - I'll just say it goes back to how I should've just made a super vague title for the makewebrequest background bug report like "onbackgrounddata() not called" or "bg broken :'(" so that nobody would be able to question whether it was *too* precise (i.e. specified too many preconditions for the bug to occur).
I'll add that I haven't just created a topic with "tags" in the title. The way I got to this error is that I clicked on the "tags" links in the top-right corner:
which lead to urls like:
https://forums.garmin.com/developer/connect-iq/f/forum-about-the-forum/tags/blocked
So Cloudflare actually blocks part of the forum
I'll add that I haven't just created a topic with "tags" in the title. The way I got to this error is that I clicked on the "tags" links in the top-right corner:
Yes, I understood that. My point was to explain that wasn't a "recursive bug" as you said, it's just two instances of the exact same bug:
- the tags links generated by the forums have urls containing "/tags"
- the topics you posted starting with the word "tags" have urls containing "/tags"
It's not the case that you were blocked for simply trying to talk about the bug, for making a post containing the links in question, or even for mentioning the word "tags" in the topic title. It's a very specific bug which is triggered for all forum urls that contain "/tags".
Ways that it's specifically *not* a "recursive bug":
- you can post the tags links themselves (and ofc the forum does this automatically), and your post won't be blocked. it's only the linked page itself that's blocked
- you can actually post topics with the word "tags" in the title, it just can't be the first word
It only *appears* to be "tragicomic" or a "recursive bug" if you assume that you were blocked simply for posting about the bug, but it's actually more of a coincidence than anything else.
If you had chosen a slightly different title for your posts, like "Can't access tags pages", they wouldn't have been blocked, and you wouldn't be posting about a tragicomic recursive bug.
So Cloudflare actually blocks part of the forum
Yes that's true in both cases.
- the tags links lead to pages that are part of the forum (presumably each page is supposed to list the topics associated with a given tag). and those pages are blocked
- the blocked topics whose titles start with "tags" are also "part of the forum"
If you mean that cloudflare blocks built-in content auto-generated by the forum, yes that's obvious.