Re: HREFs that can't be

From: Date: Fri, 02 Mar 2001 08:12:42 +0000
Subject: Re: HREFs that can't be
Groups: php.general 
Request: Send a blank email to php-general+get-42305@lists.php.net to get a copy of this message
Addressed to: php-general@lists.php.net Chris.Boget@wild.net ** Reply to note from CC Zona <cczona@nospam.invalid> Thu, 01 Mar 2001 20:05:55 -0800 > > In article <4040BBE81A9AD411BD27009027887A7C042ADD@tiger.wild.net>, > Chris.Boget@wild.net ("Boget, Chris") wrote: > > > Also, how would I set the (previously GET) vars up as session > > variables? I'd have to post to yet another script which > > would set the session variables and in turn SUBMIT (with just > > the SESSID this time) to the actual page (remember, I can no > > longer use any GET variables so the header() function would > > be out) that is the final destination... > > Just include the SID as a hidden input. It'll be POSTED to the next page > right along with your other variables. There's even a way to configure > your php.ini file so that PHP includes the hidden SID for you. I forget > which setting it is--maybe "trans-id" or something like that...? Poke > around in the the "configuration" chapter of the manual; it's in there. That won't work. Clicking on a link does not trigger sending of fields (hidden or not). There are only three places you can pass data without using forms, and using buttons, or images to trigger a POST of the data. 1. Get parameters after a ? 2. Cookies. 3. In the URL itself. Why do you want to eliminate all get params and cookies? That might have a lot of control as to what the best approach will be. Rick Widmer Internet Marketing Specialists http://www.developersdesk.com

« previous php.general (#42305) next »