Making WordPress.org

Opened 6 weeks ago

Last modified 2 weeks ago

#8449 new defect (bug)

RSS feeds on plugins.trac.wordpress.org blocked for feed readers by bot protection

Reported by: jessedyck Owned by:
Priority: normal Milestone:
Component: Trac Keywords:
Cc:

Description

The changeset log RSS feeds on plugins.trac.wordpress.org can't be fetched by automated feed readers. Bot protection appears to block the request, so the reader gets a challenge or error page instead of the RSS XML.

Example feed:
​https://plugins.trac.wordpress.org/log/elementor/?limit=100&mode=stop_on_copy&format=rss

This is published on the development tab of the plugin directory, eg:
​https://wordpress.org/plugins/elementor/#developers

Steps to reproduce

Subscribe to the URL above in a server-side feed reader (in my case, Slack's RSS app via /feed subscribe <url>, also tested with feedbin.com).

The Slack subscription fails:

Encountered a problem fetching the feed

The same URL opened in a regular browser does return valid RSS.

Expected result

The request returns a valid RSS feed to non-web browser clients. RSS feeds exist to be consumed by readers, which can't solve JavaScript or CAPTCHA challenges.

Actual result

The request returns an HTTP 403 and is blocked/challenged, so the feed can't be used.

curl -I "https://plugins.trac.wordpress.org/log/elementor/?limit=100&mode=stop_on_copy&format=rss"
HTTP/2 403 
server: nginx
date: Wed, 07 Oct 2026 15:39:23 GMT
content-type: text/html
set-cookie: _hcc=ZGMyZWUwYzRhY....; Max-Age=30; Path=/

Change History (2)

#1 @jonsurrell
3 weeks ago

I believe this is an issue across all Trac instances, Core has the same problem for example:

​https://core.trac.wordpress.org/query?component=HTML+API&order=id&desc=1&format=rss

#2 @DimitriAus
2 weeks ago

The workaround is to copy the _hcc cookie from Chrome and pass it to curl or other script.

This raises questions about the effectiveness of cookie-based bot protection. Scripts can obtain and reuse cookies, while legitimate RSS clients cannot.

Rate limiting and request-volume monitoring would be more appropriate than requiring browser verification for public RSS feeds.

Note: See TracTickets for help on using tickets.