The discussion, titled “Trouble with a RSS feed,” revolves around issues with the RSS Polling Plugin on Discourse. nathank initially reports difficulty accessing the RSS feed from www.hinz.org.nz, which fails to load in the browser and plugin. craigconstantine confirms a 403 error via curl, suggesting the server may block certain requests. Falco identifies that the feed redirects on GET requests but returns a 403 on HEAD, and recommends configuring the plugin to fetch the feed directly from the CDN URL https://cdn.ymaws.com/www.hinz.org.nz/resource/rss/news.rss, which resolves the issue for nathank. nathank then raises two new concerns: the “expand post content” button fails due to a console error, and the plugin only pulls the first paragraph of the feed, ignoring the second (more valuable) paragraph. He seeks ways to extract raw text, bypass inline styles, or target specific HTML elements like the second <p> tag, but is unsure how to configure the plugin or use CSS selectors effectively.
Continuing the discussion from Configure the Discourse RSS Polling Plugin:
Hi - I’m struggling to get the RSS Polling Plugin to work for my RSS feed: https://www.hinz.org.nz/resource/rss/news.rss
My browser (Chrome) doesn’t want to open it. But when I run it through a validator it seems to be okay:
Is there something I’m missing in the config?
Curiously, I get a 403 if I try curl …
Craigs-iMac:~ craig$ curl -I https://www.hinz.org.nz/resource/rss/news.rss
HTTP/2 403
date: Wed, 11 May 2022 14:04:59 GMT
content-type: text/html
content-length: 1233
x-datadome: protected
accept-ch: Sec-CH-UA,Sec-CH-UA-Mobile,Sec-CH-UA-Platform,Sec-CH-UA-Arch,Sec-CH-UA-Full-Version-List,Sec-CH-UA-Model,Sec-CH-Device-Memory
set-cookie: datadome=EU3BHAFHQ05_KVgwW1Wjs9oOG7yBN6ViNb-Z0zhemMzTdky84_xqOxGy~PCdj6GF2paWbjlV6YBVr8EffwN.eBXFJjRmcsp9ix7FLkAxA2yCry0Eo6sLlqchK2zbnjV; Max-Age=31536000; Domain=.hinz.org.nz; Path=/; Secure; SameSite=Lax
location: http://www.hinz.org.nz/resource/rss/news.rss
x-powered-by: ASP.NET
referrer-policy: no-referrer-when-downgrade
strict-transport-security: max-age=31536000
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
Maybe that server is picky about user-agents? …if the RSS validator can fetch it, but my curl, and the plugin cannot . . .
Looks like https://www.hinz.org.nz/resource/rss/news.rss replies to GET requests with a 301 to https://cdn.ymaws.com/www.hinz.org.nz/resource/rss/news.rss but to HEAD requests with a 403.
You can configure the plugin to download the feed from https://cdn.ymaws.com/www.hinz.org.nz/resource/rss/news.rss directly to avoid their mess.
It works perfectly!
Thank you.
I’ve got a couple of ongoing problems with this, and would love a bit more help.
I get this in the console:
The truncated post brings in just the first <p>. Unfortunately I need the second one (the first is junk).
While I can target some ugly HTML passed through from the feed and suppress it with CSS, as well as customise the “This is a companion discussion topic…” text, I’m stuck with the unfortunate inline styling that is passed through. And I miss the highly valuable 2nd paragraph.
Is there a way to get rid of all the HTML elements / styles in there and just bring in the raw text? Or better yet, a selection of the raw text (in my case the 2nd <p> only)?
The second <p> element of each, including
Is this achievable / configurable? I couldn’t work out how to use CSS selectors to achieve this with my feed.
