|
|
Posted by OmegaJunior on 02/02/07 19:52
On Fri, 02 Feb 2007 18:22:44 +0100, sid <sidwelle@alexian.net> wrote:
> On Feb 2, 1:59 am, OmegaJunior <omegajun...@spamremove.home.nl> wrote:
>> You can set the session
>> configurations to use nothing but cookies; that way it won't ever try to
>> create a sessionid in the url. Then you can create a cookie on a front
>> page which you check on a subsequent page, to see whether or not the
>> client accepts cookies. If they don't, ask them to allow their browser
>> to
>> accept cookies for your web site. Would they do that? Yes, if they value
>> their security. (Not that it's very secure by itself, but it's a start.)
>>
>>
> Can you tell me what keysnames to check ?
>
> I don't believe that the browser I was using prohibits cookies from
> being set.
> What criteria does it use to determine if cookie are enabled or not ?
>
> Sid.
>
>
>
You invent the keynames yourself. There are some reserved ones. I tend to
use something like "myApp_cookiecheck" where I replace "myApp" with an
acronym of the web site where I use it, and simply set the cookie to 1.
When a subsequent page tries to load the cookie (using
$_COOKIE['myApp_cookiecheck']) and can't read it, you can be pretty sure
the browser rejected the cookie. But why it rejected it, is worth a study
in and of itself.
You may want to take a look at
http://nl3.php.net/manual/en/function.setcookie.php
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Navigation:
[Reply to this message]
|