HREFs that can't be

From: Date: Fri, 02 Mar 2001 02:37:12 +0000
Subject: HREFs that can't be
Groups: php.general 
Request: Send a blank email to php-general+get-42271@lists.php.net to get a copy of this message
I know I've been posing some funky wierd questions all day, but today has just been one of those days... I'm just trying to get a sense of other possibilities. And to find out what's plausable and what's not. Ok, here's my situation. I've a script that generates a variable number of HREFs/anchors. Each of those HREFs can go to variable pages and also have a variable number of GET variables. So, for the sake of this example, lets say my script generates the following HTML: ----------- <a href="/hispage.php?var1=xxx&var2=yyy">Here<a/><br> <a href="/otherpage.php">There<a/><br> <a href="/thatpage.php?joe=bob">This Place<a/><br> <a href="/lapage.php?this=that&his=hers&here=there">That Place<a/><br> ----------- As you know, those variables are being passed to the linked page via GET variables. Now, here comes the oddball question: How can I (is it even possible) pass those variables to each page w/o using GETs and w/o using Cookies. Ultimately, the plan they are pushing is to make our site(s) free of all GET variables (including the SESSID; yes, you read that right) and of cookies. Also those GET variables above should be turned into session variables if and when possible, but only if the user clicks on the actual link. This is basically the environment that has been presented to me. Is such an environment possible? If so, how? What is necessary to make it work this way? If it is not, to what extent is it possible? Thanks for reading this far. Thanks, also, for fielding this question and offering any help and any insight you can on my dilema. Chris

« previous php.general (#42271) next »