Link to home
Start Free TrialLog in
Avatar of matala
matala

asked on

assigning a cookie within a VFP automation server

The following is basic question about cookies: I have a DCOM application (basically an automation sever
 created in VFP 5.0); call it classA. When classA is loaded from a web browser using foxisapi.dll, it returns an
 HTML web page asking the user to logon by furnishing a username and password. If the logon is successful, I
 use these name and password as ((input name="Cookie" type = "hidden" value = "the username and the
 password")) within all ((form)) and ((a href)) tags in subsequent web pages. This helps me identify the current
 user so that the correct data is displayed on the return web page. In this sense, the password and username are
 behaving like a cookie. The problem is that they appear as parameters at the URL when a ((a href)) link is
 clicked. With a "submit" button I put ((method="post")) in the ((form)) tag so that no parameters appear in the
 URL when the button is clicked. Is there a way to not make them appear in the case of ((a href)), so that to hide
 at least the password of the user; and how can I assign a cookie to the user and store on the user's computer?
Avatar of jbirk
jbirk

Yes cookies can do what you ask, but it's not a simple proposition.  I can post the cookie library I use (when I get home) if you want.
It comes with pretty good documentation, so you can probably just figure out how to use it.
But 1 point isn't very much incentive to do much more than that.
-josh
ASKER CERTIFIED SOLUTION
Avatar of jbirk
jbirk

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of matala

ASKER

Sorry about the 1 point.  I am running low on my balance!  I would appreciate the documentation about cookies library.  Thanks.
That's included above in the code.  The documentation is all in comments.  I think it's pretty clear, but it's so much documentation, that I would delete it all after reading it to preserve space (and reduce file size).  The documentation provided is all about how to use the code properly.  But if you were interested in knowing how each line works, just ask about the lines of code you don;t understand and I will try to explain them.

-Josh