Enable_trans_sid will put a psession key in the URL of the second (i think)
page of the session, as a method of ensuring state... at that point it can
assess if you need to keep using the URL (no cookies) or if the session
state can be maintained through cookies (no URL).
URLs, but prevent some people from using the site. Tuff call.
Personally I'd look for a way of modifying ht://dig, or write a small
program to go through your database removing "PHPSESSIDyaddayadda" from the
URLs, or SOMETHING.
Maintaining state in the URL is the only fool-proof method, so my gut
feeling is to make sure the SITE works first, then worry about logs, htdig
and other secondary problems...
on 27/09/02 5:09 AM, Bill Farrell ([EMAIL PROTECTED]) wrote:
> Hi all,
> Is there a really thorough tutorial on the use of
> session variables? Seems like there are a zillion
> options to choose from, lots of interdependent
> settings, etc, and I'm a bit confused on how to make
> it work.
> I try not to use session objects too much in any
> language as it makes the code somewhat less portable,
> but I did want to experiment with PHP's notion before
> launching off on another suite of apps. I'm starting
> with a simple fake hit counter that checks session to
> see if the counter was already dinged. It works if I
> turn on enable_transient_sid, but setting that drives
> ht://dig nuts by appending ?PHPSESSIDyaddayadda to the
> URL. Really makes a mess of the database :-)~~.
> Obviously, I'm missing something pretty fundamental.
> Any suggested reading would be appreciated (yes, I did
> read the PHP manual :-).
> Thanks in advance,
> Bill Farrell
> Multivalue and *nix Support Specialist
> Phone: (828) 667-2245
> Fax: (928) 563-5189
> Web: http://www.jwfarrell.com
> Do you Yahoo!?
> New DSL Internet Access from SBC & Yahoo!
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php