We should really have an accept header in there. Something along the lines of application/rss+xml, application/rdf+xml, */*;q=0.1. Add in application/xml and text/xml with a lower q value too. This is Section 14.1 of RFC 2616. When the new smart feed making things come we will be ready. (virtuelv of #rss1.1 on freenode told me about this).

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ricabrantes’s picture

Version: x.y.z » 7.x-dev

Any activity??

mustafau’s picture

Status: Active » Needs review
FileSize
696 bytes

Here's the first patch. Needs some testing.

cburschka’s picture

Status: Needs review » Needs work

Is it possible to test for outgoing HTTP headers with SimpleTest? If so, perhaps this can be unit-tested.

Also, don't you need the */*;q=0.1 there to act as a fallback for other types like text/xml?

mustafau’s picture

Status: Needs work » Needs review
FileSize
727 bytes

Reroll.

The parser's capabilities are very limited. I don't know if "*/*;q=0.1" makes sense for this.

cburschka’s picture

Status: Needs review » Needs work

text/xml is considered bad form and in the process of being deprecated, but that doesn't mean we can refuse to accept it when it might still be sent for valid RSS content.

So even if we don't add */* at the end, text/xml should be in there.

cburschka’s picture

Issue tags: +Needs tests

Also, test case...

jrbeeman’s picture

Issue tags: +DrupalconSF

Hopping on this for the DrupalCon Thursday code sprint

jrbeeman’s picture

I'd like to add a test for this, but I believe that the current module architecture doesn't allow a test to be written that adequately tests the headers. The function aggregator_aggregator_fetch($feed) is the API method that retrieves a feed. However, it constructs the headers, sends the drupal_http_request() and returns a boolean value. From what I can see, it looks like the intent of hook_aggregator_fetch() is to pass the $feed variable by reference, because several values in the $feed object are being set during aggregator_aggregator_fetch() that wouldn't otherwise be worth setting.

While trying to dig deeper into this issue, I've found that aggregator module simply isn't parsing items at the moment (i.e. add the RSS URL http://drupal.org/rss.xml and attempt to fetch items). Gotta run to catch my plane home, but I'll try to dig into this more over the coming days.

Jody Lynn’s picture

Version: 7.x-dev » 8.x-dev
Anonymous’s picture

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

sarmiliboyz’s picture

Version: 8.3.x-dev » 8.4.x-dev
Issue summary: View changes
Issue tags: -

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Project: Drupal core » Aggregator
Version: 9.4.x-dev » 1.x-dev
Component: aggregator.module » Code

The aggregator module has been removed from Core in 10.0.x-dev and now lives on as a contrib module. Issues in the Core queue about the aggregator module, like this one, have been moved to the contrib module queue.

larowlan’s picture

Issue tags: +Needs reroll

Needs reroll for contrib

This would live in \Drupal\aggregator\Plugin\aggregator\fetcher\DefaultFetcher now