Undefined offset: 2 in drupal_http_request() [#1567212]

Firstly, great module! Just what we were looking for.

After clicking Facebook connect, granting permissions and being redirected to the front page we are seeing this error:

Notice: Undefined offset: 2 in drupal_http_request() (line 930 of /var/www/sandbox.cyac.jp/includes/common.inc).
Notice: Undefined offset: 2 in drupal_http_request() (line 930 of /var/www/sandbox.cyac.jp/includes/common.inc).

We are being logged in correctly but this notice is appearing to users.

Comment	File	Size	Author
#4	Captura de pantalla - 130314 - 18:41:20.png	10.31 KB	juanramonperez

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

quicksketch

he/him

CreditAttribution: quicksketch commented 24 December 2012 at 20:15

Status:

Active

» Postponed (maintainer needs more info)

I've never been able to reproduce this problem and we haven't gotten any confirming reports. I'm not sure what to do about this issue. Can you provide any additional or new information? Is this problem still occuring?

Comment #2

sbilde CreditAttribution: sbilde commented 13 March 2014 at 13:37

Issue summary:

View changes

I am just starting to have the saem problem, after updating to newest Panels version: 7.x-3.4 : screenshot: http://d.pr/i/5bXi

Im using the Fboauth version: 7.x-1.6

Could anybody please point me in the right direction!?

Comment #3

niknjegovan CreditAttribution: niknjegovan commented 13 March 2014 at 20:59

Same here on a bitnami stack on AWS

Notice: Undefined offset: 2 in drupal_http_request() (line 993 of /opt/bitnami/apps/drupal/htdocs/includes/common.inc).
Notice: Undefined offset: 2 in drupal_http_request() (line 993 of /opt/bitnami/apps/drupal/htdocs/includes/common.inc).

Everything seems to login properly but this notice is being generated for some reason I don't know.

Comment #4

juanramonperez CreditAttribution: juanramonperez commented 13 March 2014 at 21:43

File	Size
Captura de pantalla - 130314 - 18:41:20.png	10.31 KB

Same here. I didn't do anything in my site. All works fine but the Notice is now showing to the users

Comment #5

Graber CreditAttribution: Graber commented 14 March 2014 at 10:39

Hi all.

The problem is that drupal_http_request assumes that status message is present in the response header.
Normal response header has it (e.g. HTTP/1.0 200 OK), while the header from facebook has only HTTP/1.0 200.

What needs to be done is a patch to drupal_http_request in common.inc to adopt it to this situation, like so:

line 996 insetead of:

list($protocol, $code, $status_message) = explode(' ', trim(array_shift($response)), 3);

we put:

  $status_data=explode(' ', trim(array_shift($response)), 3);
  if (!isset($status_data[2])) $status_data[2]='OK';
  list($protocol, $code, $status_message) = $status_data;

I just hacked drupal core. Hopefully this will be included in the next version, because I don't have permissions to contribute such patches.