Justin, et al --
...and then Justin Patrin said...
%
% Well, technically, you should be using the PEAR installer script to
% install PEAR packages. http://pear.php.net/manual/en/installation.php
Oh. Oops :-)
%
% Barring that, you can make yourself a PEAR directory somewhere and add
% it t
Well, technically, you should be using the PEAR installer script to
install PEAR packages. http://pear.php.net/manual/en/installation.php
Barring that, you can make yourself a PEAR directory somewhere and add
it to your include_path in your php.ini.
Also note that you have to have all of the de
Justin, et al --
...and then Justin Patrin said...
%
% One last thing. If all you need to do is go to a page and not navigate
% it, you could just use HTTP_Request, upon which HTTP_Client is built.
That sounds even better; I'm only going to be dealing with a couple of
pages.
% Then again, if
One last thing. If all you need to do is go to a page and not navigate
it, you could just use HTTP_Request, upon which HTTP_Client is built.
Then again, if you have multiple request to do and have to keep sending
the auth data, the Client would be best.
David T-G wrote:
Justin, et al --
...an
Justin, et al --
...and then Justin Patrin said...
%
% You can use PEAR's HTTP_Client package
% (http://pear.php.net/package/HTTP_Client) to connect to a website, do
% authentication, post forms, handle redirects, etc. It also keeps track
% of cookies.
Oh, goodie; that sounds great.
%
% He
You can use PEAR's HTTP_Client package
(http://pear.php.net/package/HTTP_Client) to connect to a website, do
authentication, post forms, handle redirects, etc. It also keeps track
of cookies.
Here's a sample (note that the URLs in this will probably not work):
require_once('HTTP/Client.php');
6 matches
Mail list logo
