oops! You are correct sir. I have a special domain (secured) set up for all my clients that I run orders through. It is the change of the domain name which causes the variables to be dropped without the <@UserReferenceArgument>. I stand corrected.
Which brings up a point which I was wondering. With the new browsers, when the domain names don't match going into secure mode, a popup appears telling the user that it is secure, but the domain names don't match. I suppose there is no way of getting rid of that short of a new Cert for every domain name. It is very annoying. > > Note, however, if you do not pass the <@UserReferenceArgument> from >> http to https, you will lose all your variables. > >Not true, the cookie is linked to the domain name, not the protocol (http >vs. https) you can switch back and forth between http and https without >losing session, and not passing the userreferenceargument. > >The only time the user session gets lost is when you explicity request an >alternate port like > >http://www.myserver.com:443/ > > > >________________________________________________________________________ >TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body -- ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
