This one's more of an fyi...

Intermittently I was seeing the message "Drupal cannot make HTTP requests... need to reset HTTP requests" on a couple of my sites, even after I had successfully configured and used content push on the sites. Clearing the cache, cron, restarting Apache... I couldn't determine how to reset the failure value. If I gave it enough time (day), it would possibly clear up and work again. The bottom line, I couldn't diagnose the cause or fix.

Currently I am using the module http://drupal.org/project/http_request_fail_reset and resetting the value every hour. Don't think this is a good long term solution, but I haven't had a problem since enabling it.

Comments

Alex Andrascu’s picture

Alex Andrascu commented

I'm in the same pot too. Is there a way to reset that manually instead automatically ?

Alex Andrascu’s picture

Alex Andrascu commented

Found the solution here
#245990: HTTP request testing unreliable and may be undesirable

---------------------------------
We solved the problem with "HTTP request status fails" on Drupal 6.19 by putting this line in the end of settings.php.

$conf['drupal_http_request_fails'] = FALSE;

------------------------------

joachim’s picture

joachim commented

Neat trick! :D

wolv3rin3’s picture

wolv3rin3 commented

So, it seems the common understanding is that the HTTP request status is unreliable and doesn't necessarily indicate a true problem with the system. Yes? If that's the case, then the settings.php solution above makes sense.

However, I did run into a problem with Content Push not working because of the HTTP request status. I installed everything correctly on both my "Sending" and "Receiving" sites. I tested the connections and they worked correctly on both sites. A few hours later I tested a content push from my Send to Receive site, which displayed a success message. I checked to confirm on my Receive site, and discovered an empty node had been created - meaning there was a "new" tag and line in my site content list, but there was no data at all. I rechecked and tested the connected on my Receiving site and received the HTTP failure warning. I then reset the HTTP request status, ran a test and re-pushed content and everything worked correctly.

It seems that when the HTTP request status fails, it does interrupt Content Push. Is this just because it will drop connection if the status is set as failing? Or is there really a connection issue that needs to be addressed?

joachim’s picture

joachim commented
Project: Content push » Web Service Clients
Version: 6.x-1.0-alpha3 » 6.x-2.x-dev

This is actually in Clients.

The code is:

  function callMethodArray($method, $method_params = array()) {
    // If HTTP requests are enabled, report the error and do nothing.
    // (Cribbed from Content distribution module.)
    if (variable_get('drupal_http_request_fails', FALSE) == TRUE) {
      drupal_set_message(t('Drupal is unable to make HTTP requests. Please reset the HTTP request status.'), 'error', FALSE);
      watchdog('clients', 'Drupal is unable to make HTTP requests. Please reset the HTTP request status.', array(), WATCHDOG_CRITICAL);
      return;
    }

The code checks the drupal_http_request_fails variable and bails if it's set.

We could drop that check, I guess.

wolv3rin3’s picture

wolv3rin3 commented

I see that warning displayed when I run a connection test, but I haven't seen it displayed when I'm pushing content if the "Receiving" site HTTP request fails is set to True.

So, I'd agree to either a) pull it if it's not doing anything or b) make sure there's a warning when pushing content.

Helpful?

greta_drupal’s picture

greta_drupal commented

So, add $conf['drupal_http_request_fails'] = FALSE; to the settings.php file of the slave sties only, correct?

greta_drupal’s picture

greta_drupal commented

I noticed that the Content Distribution module has a reset button for this in the UI. Might be a good (easy?) feature to port over to Content Push. (Sorry, no, cannot write the patch...yet.)

joachim’s picture

joachim commented

> So, add $conf['drupal_http_request_fails'] = FALSE; to the settings.php file of the slave sties only, correct?

Add it to both -- both master and slave make HTTP requests in a Content Push setup.