yes I can reproduce it also...
I too can hit one box and see it come and go...
Chris,
we have see this behavior before that bug was fixed in revision
[17819].
-my $cgi = $CGI::qqq ||= CGI->new();
+my $cgi = $CGI::qqq || CGI->new();
There must still be some code in production setting up the $CGI::qqq
thus tainting the httpd thread..
you can quickly reproduce it by running this a few times...
for i in 1 2 3 4 5 6 7 8 9 0; do curl "http://api09.eventful.com/json/users/login?app_key=test_key&user=&user_key=&json_request_id=$i
"; done
Then run without a json_request_id a few times
for i in 1 2 3 4 5 6 7 8 9 0; do curl "http://api09.eventful.com/json/users/login?app_key=test_key&user=&user_key=&;
"; done
I took a quick look but don't see the leak yet..
Lets take another look in the morning...
if we don't find it we can do a few things for a quick fix.
Thank you very much Ted for tracking down this issue.
-Dan
On Jun 18, 2008, at 11:24 PM, Chris Radcliff wrote:
Hm. I can't seem to reproduce that. I get JSON every time, no JSONP
at all, even with the exact same curl commnd. Are you still able to
get this result?
~chris
On Jun 18, 2008, at 9:44 PM, Edward O'Connor wrote:
It's not a Python problem, it's an issue with the JSON handler at
Eventful's end. Basically, sometimes the response is JSON, and
sometimes
it's JSONP. E.g.:
% curl "http://api.eventful.com/json/users/login?app_key=test_key&user=&user_key=
"
{"nonce":"3740583121","string":"Authorization
Required","description":"Please supply a user authentication response
using the nonce provided."}
% curl "http://api.eventful.com/json/users/login?app_key=test_key&user=&user_key=
"
var obj = {"nonce":"4740583121","string":"Authorization
Required","description":"Please supply a user authentication response
using the nonce provided."}; EVDB.API._complete(1, obj);
