Da'oud

Thanks again for the response.

I don't think that was my problem. I tested it on Mac Netscape and IE and it
worked fine. I tested on the PC and the cookie was being set in Netscape but
not being read. It didn't seem to be set and obviously not read in IE.

I host most of my projects on NT with IIS. I may go back to trying the
cookies to see if they work there. Your confidence puts a little curiuosity
back in the mix. Maybe I'll try it again soon.

For now my cable modem is out. They said they'll send someone to check it
out in a week and a half. It's killin' me.

Have a good weekend.

Tracy

> Subject: Cookie Weirdness (Was: Login/password Help?)
> From: "Daoud Rashid" <daoud.rashid@mailcity.com>
> Date: Fri, 14 Jul 2000 04:41:58 +1200
>
> Hi Tracy,
>
> Hmm...the first time I tested out my site online using Web*,
> pages weren't refreshing properly, people were being shown the
> login screen when they were already logged in, etc.
>
> Like you, everything worked fine on my development machine (which
> was also using Web*).
>
> I thought this had to do with cookies not being set on the client
> machine (it was a PC), but it turned out that the proxy that the
> PC was connected to was supplying outdated pages (rather than
> getting them from the Web* server).
>
> The reason your tokens work well is probably because they are
> somehow forcing pages to be reloaded from the server.
>
> If the value of the token changes, the proxy will think that a
> completely new page is being requested...and will contact the
> Web* server to supply it.
>
> However, you might fall into the same 'cached pages being
> supplied' trap if you return to a page which contains data that
> has just been modified (i.e. the token values don't change, so
> the proxy assumes it's alright to supply the now outdated page
> from it's cache).
>
> I got around this problem (by sticking with cookies) and simply
> appending a new lasso session id to the end of each page that I
> want to always be supplied from my Web* server.
>
> If you're using forms, you simply need to have a hidden field on
> the form called 'the_session' (or whatever) and use the
> [Lasso_SessionID] tag to give it a value.
>
> That way, the user isn't ever confronted with a long string of
> junk in their browser's location bar.
>
> The other option is to expire all pages immediately (using the
> Meta expires tag), but this means that users will not be able to
> click the back button in their browser window without having to
> press the reload button.
>
> I hope this makes sense (and helps with your situation).
>
> Regards,
> Da'oud


-----------------------------------------------------------------------
To Unsubscribe: <mailto:LassoStudioDW-off@blueworld.com>
List Archives :
<http:////listsearch.blueworld.com/LassoStudioDWSearch.lasso>
Blue World Support Central : <http:////support.blueworld.com/>
Support Inquiries: <http:////support.blueworld.com/supportinquiry.lasso>
Note: Lasso Studio for Dreamweaver Talk is not an official technical
support forum.