So apparently the #RSS URL for #NINA changed. Sadly the new one makes the same old mistake by sending the _wrong_ Content-Type making my reader trying to parse it as JSON feed. Proxy rewrite it is again *sigh
For nginx this could look like this:
location /fds-nina-feed {
proxy_pass https://warnung.bund.de/api31/mowas/rss/082370000000.rss;
proxy_set_header Accept "application/rss+xml;q=0.9,image/webp,*/*;q=0.8";
proxy_hide_header Content-Type;
add_header Content-Type "application/rss+xml; charset=utf-8";
}
Find more broken feeds at https://warnung.bund.de/meldungen
@beko Techniker ist informiert.
Remote Reply
Original Comment URL
Your Profile
Why do I need to enter my profile?
This site is part of the ⁂ open social web, a network of interconnected social platforms (like Mastodon, Pixelfed, Friendica, and others). Unlike centralized social media, your account lives on a platform of your choice, and you can interact with people across different platforms.
By entering your profile, we can send you to your account where you can complete this action.
@beko still broken.Shipped via myracloud. Seems to be an exceptional hard task to ship ".rss" with Content-Type "application/rss+xml; charset=utf-8" with that.
Remote Reply
Original Comment URL
Your Profile
Why do I need to enter my profile?
This site is part of the ⁂ open social web, a network of interconnected social platforms (like Mastodon, Pixelfed, Friendica, and others). Unlike centralized social media, your account lives on a platform of your choice, and you can interact with people across different platforms.
By entering your profile, we can send you to your account where you can complete this action.