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

status changed; resolution set

status changed from assigned to closedresolution set to wontfix More users are going to reference a blog, instead of a feed, and expect it to work than are going to point it at a malformed feed like...

View Article



keywords changed

keywords2nd-opinion removed

View Article

Article 19

personally, I'd suggest forcing. after all, if a user decides to grab a feed using an rss widget, we could safely assume that it's a feed's url indeed. the idea behavior, though, would be to do: if...

View Article

keywords changed

keywords2nd-opinion added; reporter-feedback removed Replying to Denis-de-Bernardy: so wontfix, I take it? The wontfix is for changing the behaviour of SimplePie upstream to accept text/plain as a...

View Article

Article 17

so wontfix, I take it?

View Article


Article 16

I'll change handling of text/plain (and any other bit of Content-Type sniffing) in SimplePie if and only if you can convince Adam/Ian to change ​http://tools.ietf.org/id/draft-abarth-mime-sniff....

View Article

keywords, status changed; owner set

keywordsreporter-feedback added; commit removed owner set to westistatus changed from new to assigned I think the best option here is to turn off auto-discovery in SimplePie. rmccue is there any...

View Article

summary changed

summary changed from SimplePie doesn't like rss 0.91? to SimplePie auto-detection ignores feeds with incorrect content-type in HTTP header

View Article


keywords changed

keywordscommit added; 2nd-opinion removed @dev: please commit or wontfix, so we can remove ticket clutter.

View Article


Article 12

Replying to hakre: Replying to DD32: -1 for forcing it. By forcing it, You're preventing any true non-feeds from displaying an error. no, in this case (the feed itself is valid, see w3c validation...

View Article

Article 11

Replying to DD32: -1 for forcing it. By forcing it, You're preventing any true non-feeds from displaying an error. no, in this case (the feed itself is valid, see w3c validation results) if you not...

View Article

Article 10

Replying to rmccue: [...] As far as I can see, there's no point in adding an upstream patch to SP. I'm fairly sure that the RSS specification, somewhere, mentions that a correct MIME type must be...

View Article

Article 9

Magpie itself doesn't include built-in autodiscovery, so that would have needed to be provided by WP itself. You can always run SP's autodiscovery manually if needed.

View Article


Article 8

So The only downside of using force_feed() is that we loose auto-search for feeds, ie. if someone enters '​http://dd32.id.au/' instead of '​http://dd32.id.au/feed/' then they'll get no feed displayed....

View Article

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
Browsing all 87 articles
Browse latest View live




Latest Images