Bug #31944 for WWW-Facebook-API: Query string parameters not taken into account

Thu Dec 27 18:33:34 2007 briac [...] cpan.org - Ticket created

Subject:

Query string parameters not taken into account

When using CGI.pm as $facebook->query() object, it seems that there is no way to get the URL query string in the application. Since Facebook always makes a POST request to the server, CGI.pm bypass the $ENV{QUERY_STRING} parsing and only use Facebook parameters and POST'ed form parameters. I guess it is not really a WWW::Facebook::API bug but it is rather annoying. I bypass this limitation by calling, although it could have the side effect of having unwanted multiple values (see #31620) $facebook->query->parse_params($ENV{QUERY_STRING}) -- briac

Tue Jan 29 22:41:37 2008 unobe [...] cpan.org - Taken

Wed Jan 30 02:17:07 2008 unobe@cpan.org - Correspondence added

Subject:	Re: [rt.cpan.org #31944] Query string parameters not taken into account
Date:	Tue, 29 Jan 2008 23:15:50 -0800
To:	Briac Pilpre via RT <bug-WWW-Facebook-API [...] rt.cpan.org>
From:	David Romano <unobe [...] cpan.org>

Hi Briac, Briac Pilpre via RT wrote on Thu, Dec 27, 2007 at 03:33:37PM PST: Show quoted text

> When using CGI.pm as $facebook->query() object, it seems that there is > no way to get the URL query string in the application. > > Since Facebook always makes a POST request to the server, CGI.pm bypass > the $ENV{QUERY_STRING} parsing and only use Facebook parameters and > POST'ed form parameters. > > I guess it is not really a WWW::Facebook::API bug but it is rather > annoying. I bypass this limitation by calling, although it could have > the side effect of having unwanted multiple values (see #31620) > > $facebook->query->parse_params($ENV{QUERY_STRING})

Thanks for the report, and sorry for such a late response. Do you have any suggestions (e.g., a patch) that will integrate the parsing of the $ENV{QUERY_STRING} into the module? Would you prefer just another method that simply calls what you have above, or would you like it to want it to fill in any parameters from the query string into the params hash? As of now, I've addressed RT#31620 by adding a FAQ to the latest version in the googlecode repo to warn against using GET. Let me know of any suggestions, - David -- "The only way we can be of use to God is to let Him take us though the crooks and crannies of our own characters. It is astounding how ignorant we are about ourselves." -- Oswald Chambers, My Utmost for His Highest, January 12

Wed Jan 30 02:17:10 2008 The RT System itself - Status changed from 'new' to 'open'

Mon May 26 03:03:54 2008 unobe [...] cpan.org - Status changed from 'open' to 'stalled'

Wed Jul 16 12:56:20 2008 clscott [...] cpan.org - Correspondence added

When there is POST data present CGI.pm always enables access to GET parameters via the $q->url_param method to allow your the application to decide how to deal with conflicts. http://search.cpan.org/dist/CGI.pm/CGI.pm#MIXING_POST_AND_URL_PARAMETERS I have had no problem using this approach in conjunction with WWW:::Facebook::API Clayton On Thu Dec 27 18:33:34 2007, BRIAC wrote: Show quoted text

> When using CGI.pm as $facebook->query() object, it seems that there is > no way to get the URL query string in the application. > > Since Facebook always makes a POST request to the server, CGI.pm bypass > the $ENV{QUERY_STRING} parsing and only use Facebook parameters and > POST'ed form parameters. > > I guess it is not really a WWW::Facebook::API bug but it is rather > annoying. I bypass this limitation by calling, although it could have > the side effect of having unwanted multiple values (see #31620) > > $facebook->query->parse_params($ENV{QUERY_STRING})

Wed Jul 16 12:56:23 2008 The RT System itself - Status changed from 'stalled' to 'open'

Mon Sep 29 21:40:45 2008 clscott [...] cpan.org - Correspondence added

Since there has been no more discussion I will consider this matter closed

Mon Sep 29 21:40:47 2008 clscott [...] cpan.org - Status changed from 'open' to 'resolved'