|
|
 Erick Bajao - 2005-11-15 07:58:48 - In reply to message 10 from Manuel Lemos
Hi, I'm back, just stopped from trying to make that login script work for a while and finished other tasks first, but here I am again.. Gonna give it another shot...=) Anyway, I updated my http protocol client class and my test_http script which used to work with the older version of your class and get through the proxy, now doesn't work and has this Error: Could not process the SASL proxy authentication step: Basic authentication was finished without success.
I don't know what went wrong here since I didn't change anything in my script, I just migrated it to the newer version of the class..
Thanks for helping again! =)
 Manuel Lemos - 2005-11-15 18:51:23 - In reply to message 11 from Erick Bajao
There was a bug in the HTTP class that was preventing it to encode authentication responses correctly with some mechanisms, like HTTP Basic.
I just uploaded a fixed version. Thank you for reporting.
 Erick Bajao - 2005-11-16 06:46:10 - In reply to message 12 from Manuel Lemos
Hi, I'm having a hard time getting POST to work with the SQUID proxy.. I'm trying to send a POST request to an https site but it seems that it is unsupported by SQUID... Is there something I can do get it through the proxy?
 Manuel Lemos - 2005-11-16 21:35:46 - In reply to message 13 from Erick Bajao
I have reproduced the problem. It is returning error 400 Bad request .
It turns out that relaying SSL requests over HTTP proxies in the usual way may lead to security problems because the traffic between the HTTP client and the proxy server can still be sniffed. That is why Squid refuses relaying SSL requests over HTTP connections.
The solution is to establish a remote connection with the SSL server via proxy using the CONNECT command. Only after the remote server accepts the connection, the SSL protocol begins. The proxy just forwards and recieves opaque data.
The problem with this is that AFAIK there is no way to start SSL after it was already started a normal connection with PHP fsockopen(). I need more time to study the problem and see if there is a workaround.
 Erick Bajao - 2005-11-17 06:44:41 - In reply to message 14 from Manuel Lemos
Hi, for the meantime I uploaded my php scripts on a webserever so I wouldn't deal with the proxy... Anyway, I started trying to login automaically to yahoo but still no luck.. It keeps on redirecting me back to the login page.. I'm not sure if I'm doing the 'cookie' stuff right, you can test my script here: http://gallery.ph/frederick/php/httpclient/Test2.php
Thanks!
 Erick Bajao - 2005-11-17 10:04:00 - In reply to message 15 from Erick Bajao
It think it is only the Cookie 'B' that is always being sent and the other cookies like F,Y,and T are left behind.. Maybe that's why I'm always redirected to the login page..
 Manuel Lemos - 2005-11-17 18:18:06 - In reply to message 16 from Erick Bajao
There was a bug in the interpretation of secure option of the cookies. It was preventing to send non-secure cookies to non-secure sites. I just uploaded a fixed version. You may try it now.
 Erick Bajao - 2005-11-18 02:35:56 - In reply to message 17 from Manuel Lemos
Yes! I finally made it...=) Thank you very much for your help.. I'll just clean my code up then I'll submit it as a class.. Again, Thank you very much! =)
 Jason Brumwell - 2005-12-03 21:00:18 - In reply to message 18 from Erick Bajao
I am having this exact same problem I was able to get hotmail up and running fine but when I check the cookie array I get B part printing only. I tried using the class mentioned in here but the class file has no functions just a corrupted file it looks like.
Any help would be greatly appreciated.
Jay
 Jason Brumwell - 2005-12-03 21:01:55 - In reply to message 19 from Jason Brumwell
sorry my response may be confusing I am having problems with yahoo not hotmail. sorry for the confusion
|