Date:  03/23/2011 09:37:31 PM Msg ID:  004254
From:  FoxWeb Support Thread:  004250
Subject:  Re: Issues with old passcook.prg
It's interesting to me that you are specifying different values for oPass.UserTable in fw_enter and the various PRG files. Is this intentional? I don't know if the problem is related to this, but it's possible.
Another possible cause of the problem would be if you were using the Response, Session or Auth objects. The PassCook code was written for FoxWeb version 1 (15 years ago!) and relies on the all html_out variable. If you use the Response, Session, or Auth objects, FoxWeb will simply ignore any content placed in html_out.
FoxWeb Support Team email
Sent by jweesies on 03/23/2011 10:00:01 AM:
DO passcook
oPass.Usertable = 'c:\program files\foxweb\users'
oPass.IdleTime = 3600

prg from app:
    opass.usertable = (cPath) + 'arcust01'
    opass.Header = "<center>xxxxxxx Site<br>User Authentication</center>"

    IF !opass.Authenticate(.T.)

Sent by FoxWeb Support on 03/22/2011 04:36:25 PM:
Please post (or email) the contents of fw_enter.prg. Also, provide us with the code that enforces authentication in a typical protected program. 
FoxWeb Support Team email
Sent by jweesies on 03/22/2011 04:29:56 PM:
We have an older Foxweb application running under version 2.6.  The app is built under the 1.x style with procedures within a prg and using html_out to return html.  The app uses the passcook.prg program to control user authentication and runs without issue.
We recently installed the newer version, 4.3, on a new PC.  I copied the app and passcook.prg from the old PC to the Foxweb folder of the new PC and it would run fine, except some procedures would error out with an oPass object not found error (most run fine).  I then copied fw_enter.prg to the Foxweb folder from the old server to the new server and now every page pops up the authentication page upon submit, as if it is losing the cookie.  oPass.IdleTime is set to 3600 seconds.
Please advise.