Enabling HTTPRL module breaks Update module

Not sure if this is the same issue I was having.... The update screen would say "Failed to get available update data for __ projects." I found that by disabling "Use httprl to handle drupal_http_request" it works again.

I'm guessing this has been a problem for at least a month, although I just noticed it.

My production and dev sites were running 7.x-1.14+32-dev and 7.x-1.14+39-dev

Same issue for me, since ca. 2 Weeks, for the production and dev version of this module.
Option "Use httprl to handle drupal_http_request" activated or not - both breaks update module. Only deaktivate httprl module, update module works again.

It worked! Glad i found this! I've been stuck for weeks already.

I had this exact same issue with the failed Drupal updates and unchecking the "Use httprl to handle drupal_http_request" option on the HTTPRL settings page did solve the problem for me.

I have the same problem and that makes me wonder if the module works in general as there are no errors when trying to fetch drupal updates.

I found this thread through AdvAgg. I thought it was the culprit since the issue cropped up around December. It would appear that HTTPRL is malforming URL requests. Digging into this.

Just in case: https://www.drupal.org/node/2647144

Subscribe same issue here.

This has only come up as a problem recently. My guess would be something changed in the formatting of the Update requests that causes it to break with HTTPRL, but still work correctly with core.

The issue title should be changed to be more easily picked up in online searches.

I forgot to point out that the issue is specifically related to the option: Use httprl to handle drupal_http_request.

If you disable it, the problem goes away.

Thanks Shane,

I have disabled it and everything is OK now.

In my view, the problem has settled again - yesterday the module works correctly again with all options enabled.

This was probably caused when drupal.org started redirecting updates.drupal.org traffic to HTTPS on January 12, and fixed when that was rolled back on February 8 (see #2646894: Redirect http://updates.drupal.org and http://ftp.drupal.org to https version (roll back the updates.drupal.org part?)).

However it is still probably worth figuring out what goes wrong here, since we do want to have Drupal core start making these requests over HTTPS directly via #1538118: Update status does not verify the identity or authenticity of the release history URL.

HTTPRL in general works 100 times more reliable than drupal_http_request(). As I made hundreds of tests in linkchecker to verify how good it handles special conditions and mikey fixed all bugs in httprl - I tend to say this must be very specific situations. Maybe the already known ones...

All you guys here need to share your php version and if you have curl installed. If curl is installed you also need to share info what CA list you have or better if the root ca d.o used is integrated or not.

A simple curl request to https://ftp.drupal.org/ may answer what's wrong. I guess it is not the 302 redirect that caused a failure. It should be the certificate or #1879970: drupal_http_request fails when remote server is using openssl v1.0.0.

Adding another reference
https://www.drupal.org/node/2675912

In my case it was an interesting thing. I had this module, but it was disabled. After enabling and disabling the module again updates became functional.

And about clearing (#18 and mentioned in old topic https://www.drupal.org/node/1090528) - I did it, cleared cache_update table, but there was a little effect after it.