Joomla FIX for “No HTTP response code found”

FIX for “No HTTP response code found”

(NOTE: This is for Joomla 2.5.16 ONLY!)

When attempting to upgrade an old Joomla site from v2.5.16 to 2.5.27, “No HTTP response code found” appears in the Joomla Control Panel, under the RSFirewall! Control Panel Module section.

And when I go to: Components > Joomla! Update all I get is the frustrating: “You already have the latest Joomla! version, 2.5.16.” And there’s no Upgrade available.

RSJoomla has the FIX for the No HTTP response code found error

If you have recently updated your website to the latest Joomla! version – 2.5.16, you might get the following message in the RSFirewall! CPanel Module‘s RSFirewall! and Joomla! Update status sections:

No HTTP response code found

The error message is generated by a bug in Joomla!’s framework (it doesn’t take into account that cURL wrappers are keeping headers data differently than regular HTTP wrappers), and it occurs only when PHP is compiled using the “–with-curlwrappers” feature. To verify if this is your case, please head to:
Site >> System Information >> PHP Information and look under Configure Command , you should find “–with-curlwrappers” amongst the configuration options.

Fortunately, this inconvenience can be corrected using a simple fix:

  • Head to /libraries/joomla/http/transport/ and edit the stream.php file
  • Scroll down to the line containing // Get the response code from the first offset of the response headers.
  • Add the following code before it:

if (isset($headers['headers'])) {
$headers = $headers['headers'];

Source: No HTTP response code found


After editing the stream.php file the error message went away and I was able to update Joomla.

In order for the Joomla Update page to properly display an available update, go to: Extensions > Extension Manage, click the Update tab, then click the Purge Cache button. Then go back to Components > Joomla Update and a Joomla update should be available.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *