I'm adding additional bounty to my problem for anyone who can help me fix
it.
I'll send you a Rio Cali Sport 256 MB MP3 player - new in box. Comes with
the sport ear buds, arm strap, few other accessories. You can google it for
the details of it. Great for a stocking stuffer or as an extra gadget for
kicks (as if we all dont have enough). =D
To restate the problem for those that have forgotten, one server is working
(win 2k, other is not win 2k3) - same code, same versions of everything.
I've created a page for you to view the code / the verbose data / the
phpInfo() for the two servers. Its a script to auto-login to a site - not
particularly yahoo, the problem occurs with all cookie based logins, so
using this yahoo script as an example. Again, the win2k server ==IS==
working with that code - so its dosent appear to be a code issue.
You can view the debug information here : http://70.84.198.254/index.html
thanks again,
Nate Nielsen
[EMAIL PROTECTED]
----- Original Message -----
From: "Curt Zirzow" <[EMAIL PROTECTED]>
To: <php-general@lists.php.net>
Sent: Friday, November 18, 2005 11:04 PM
Subject: Re: [PHP] php + cURL issue
On Fri, Nov 18, 2005 at 06:08:16PM -0600, Nate Nielsen wrote:
Okay, I've added the verbose output to copare exactly what is happening
between the two versions - thanks to Curt, the verbose info shows there
IS
something different happening.
To recap, the code is exactly the same, the php version is the same (same
files even), the php.ini is the same (except drive letters), the curl
version is exactly the same (libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3).
The
only difference is that one server is Win2k and the other is Win2003
(and
of course one is working and other is not).
yeah, it does seem to be *not* a bug in curl versions.
Now it is very clear that something different is happening on the two
different servers. I've created a page to list the phpInfo() data, the
code that is being run, and the VERBOSE information outputted by cURL.
You can view the information here : http://70.84.198.254/index.html
ok.. the key thing i noticed in that nice little side by side
display you put together is this:
When you are sending the first post data look at the end of it
curl is complaining about something:
Ok side:
name=login_form&.src=auc&.tries=1&.done=TML
4.01//EN&.md5=&.hash=&.js=&.partner=&.slogin=adsherrouse&.intl=us&.fUpdate=&.prelog=&.bid=&.aucid=&.challenge=.01//EN&.yplus=&.chldID=&pkg=&hasMsgr=0&passwd=doglogan&submit=Sign
In< HTTP/1.1 302 Found
Bad Side:
name=login_form&.src=auc&.tries=1&.done=TML
4.01//EN&.md5=&.hash=&.js=&.partner=&.slogin=adsherrouse&.intl=us&.fUpdate=&.prelog=&.bid=&.aucid=&.challenge=.01//EN&.yplus=&.chldID=&pkg=&hasMsgr=0&passwd=doglogan&submit=Sign
In* Curl_xxx_rcvs returned -1, block = TRUE
You will notice that the ok side is sends back a 302 while the bad
side is returning an error from curl.
I'm not sure what that Curl_xxx_rcvs.. line means but it seems is
the source of the problem.
A other thing you would want to compare is the actual results that
come back from the request.
On the otherhand, what you seem to be doing is very likely to break
sooner than later, i'm not sure why you want to proxy a complex web
authentication system such as yahoo's
Curt.
--
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
