Question about Anubis now blocking ticket discussions.json ('RSS') endpoint

Infrastructure
1

Anubis has been active on the GNOME GitLab for a while now, but up until recently some endpoints such as the /discussions.json endpoint every issue has, e.g. https://gitlab.gnome.org/GNOME/mutter/-/issues/4244/discussions.json, were not part of this.

Whilst Anubis by default tries not to block RSS feeds, this endpoint likely isn’t detected as one, which is unfortunate since whilst GitLab supports RSS feeds for the issue list of a repository, it doesn’t have one per ticket, meaning the discussions JSON is the ‘next best thing’. Other alternatives include using the actual GraphQL/REST API, which is more cumbersome for e.g. an RSS reader that supports conversion scripts (e.g. Liferea).

I’m wondering if there is any chance the team would consider lifting the block (only) for this endpoint since it can be seen a bit as ‘the RSS feed for a ticket’? :slight_smile:

Also happy to report this elsewhere if necessary.

Thanks!

2

There’s an exception rule for .{rss,xml,atom}, any idea why you’re not using something like https://gitlab.gnome.org/GNOME/mutter/-/issues/4244/discussions.rss instead?

1 Like
3

No reason at all except that I simply didn’t know there was an alternative endpoint with the same contents that is called discussions.rss and isn’t blocked. I switched my scripts over to that and it works, thanks a bunch!