Quantcast
Channel: WordPress Trac: Ticket #9689: SimplePie auto-detection ignores feeds with incorrect content-type in HTTP header
Browsing all 87 articles
Browse latest View live

Article 7

I recommend forcing it. As far as I'm aware, forcing it will simply just skip the content-type check, but any parse errors will still occur if it can't be parsed. Ah.. Ok, Then Forcing it sounds...

View Article


Article 6

I recommend forcing it. As far as I'm aware, forcing it will simply just skip the content-type check, but any parse errors will still occur if it can't be parsed. Of course, the real solution would be...

View Article


component changed; cc set

ccrmccue added component changed from Widgets to Feeds -1 for forcing it. By forcing it, You're preventing any true non-feeds from displaying an error. This needs to be sent upstream to SimplePie, to...

View Article

keywords changed

keywordshas-patch added

View Article

Article 3

This is a flaw with simple pie. The automatic Feed locating mechnaism does not identify "text/plain" as a valid contenttype for a feed. Technically spoken it is not a valid contenttype. Since the...

View Article


attachment set

attachment set to 9689.2.patch Propper SimplePie Configuration to not auto-locate (which can fail)

View Article

Article 0

I tried the Feed in the browser: It was displayed, but Opera didn't display it as Feed. I tried the Feed on a RSS Reader in the Dashboard: RSS Error: A feed could not be found at...

View Article
Browsing all 87 articles
Browse latest View live