Login to web mail - libUrlSetAuthCallback?

[VHD]

Hi Andre,

Thanks for the info. I installed liveHTTPheaders and you are right, the problem is "cookie" related.

I copied the header from liveHTTPheaders into rev and I now get "Your session has timed out". However When I use a web browser the session is still active!
(I noticed that the HTTP header contains a line that says: Cookie: SID0=10982345297)

Ben



*********** REPLY SEPARATOR  ***********

On 27/10/2004 at 2:56 PM Andre Garzia wrote:

>On Oct 27, 2004, at 8:58 AM, VHD wrote:
>
>> When using a normal browser it seems that there are a few page 
>> redirections before I am able to view my emails.
>> Also if I type "http://user:pswd@domain.com" into my browser I can log 
>> in without a problem but this does not work with the URL command.
>
>Ben,
>
>probably the server is trying to set a cookie which works fine in the 
>browser, but not in Rev. One way to fool proof this is to erase your 
>current cookies, configure your browser not to accept them, then try to 
>access your webmail, if everything is okay, then your problem is not 
>cookie related but I am very positive about cookies being your problem. 
>If this is so, then you must see how this cookies are stored, and fake 
>them to use your webmail. I don't think your webmail cookie will be 
>encripted, so a quick look in your cookie files or installing a HTTP 
>"debugger" (there are some for Firefox, like liveHTTPHeaders) to see 
>the http traffic, this way, if you search long carefully enough, you'll 
>find the response where the server sets your login cookies. This should 
>do the trick. If you use standard webmail packages you might want to 
>share with us, this code! :D
>
>Cheers
>andre
>
>-- 
>Andre Alves Garzia ð 2004 ð BRAZIL
>http://studio.soapdog.org
>
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>http://lists.runrev.com/mailman/listinfo/use-revolution
>
>
>
>__________ NOD32 1.909 (20041028) Information __________
>
>This message was checked by NOD32 antivirus system.
>http://www.nod32.com