Rahmin,
As best practice you should secure your login data by sending it over
https.
Curl handles cookies rather well and should work for your needs.
Regards,
Elijah Insua
I'm currently building an API to connect to an HTTPS server. My first
script POSTs login data as cleartext by way of cURL. The HTTPS server
throws a secure cookie back at me, set to expire within 24 hours. So
far, so good.
Within that 24 hour period, I'd like a separate script (on the same
server) to make subsequent requests; passing the authentication along
such that HTTPS knows who I am.
What's the best way to do that?
Am I trying to re-invent the wheel here?
_______________________________________________
New York PHP Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
NYPHPCon 2006 Presentations Online
http://www.nyphpcon.com
Show Your Participation in New York PHP
http://www.nyphp.org/show_participation.php
_______________________________________________
New York PHP Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
NYPHPCon 2006 Presentations Online
http://www.nyphpcon.com
Show Your Participation in New York PHP
http://www.nyphp.org/show_participation.php
