Feeds using an rss-http content type are now served as application/octet-stream

[johnbillion]

In r36230, rss-http was removed as an allowed content type for feeds as it's not used in core. This means that any custom feeds that are using that content type are now being served as application/octet-stream instead of text/xml, which means the client attempts to download the feed.

This problem has been seen on some live sites hosted on WP.com VIP, breaking some custom feeds.

[swissspidy]

Duplicate of #36334? The bug was reported there but I couldn't really reproduce it.

[johnbillion]

Duplicate of #36334.

[johnbillion]

Actually, #36334 is close but not quite the same. That issue is about the inability to override the feed's mime type via a filter to get past the issue of application/octet-stream being the default content type for custom feed types.

[swissspidy]

@johnbillion I see. Thanks for the clarification. In that case, 36620.patch​ seems fine to me.

[johnbillion]

In 37282:

Feeds: Revert [36230] which removed the rss-http feed content type. Removing this means that any feeds which are using this feed content type are now being served as application/octet-stream instead of text/xml.

See #36620

[stevenkword]

Looks like this should be closed now?

[swissspidy]

@stevenkword After it has been backported to 4.5.1

[johnbillion]

In 37284:

Feeds: Revert [36230] which removed the rss-http feed content type. Removing this means that any feeds which are using this feed content type are now being served as application/octet-stream instead of text/xml.

See #36620

Merges [37282] to the 4.5 branch.