Re: [PATCH] session.cache_limiter = none

On Tue, 2002-10-08 at 12:19, Markus Fischer wrote: > On Tue, Oct 08, 2002 at 12:05:55PM +0200, Bastiaan Bakker wrote : > > The new dcoumentation still may be a bit confusing, because 'or leave > > this empty' may be interpreted as 'don't set session.cache_limiter'. > > In > > the latter case PHP defaults to 'nocache' rather than 'no cache > > limiting'. Also the last comma in {nocache,private,public,} is easy to > > miss. > > Yes, it may not be that clear. I suggest you open a bug at > bugs.php.net about this issue so a) it doesn't get lost and > b) as soon as someone comes up with a more descriptive text > he can fix it. > > - Markus > OK, I will. BTW. I found out why leaving the option empty also works in 4.2.3: the cache_limiter function tries to find the limiter corresponding with ''. As it cannot find it, it does nothing, but simply returns with error code -1. The calling function simply ignores the return code and continues processing. Unfortunately this also causes misspellings like 'session.cache_limiter=pivate' to go unnoticed. Cheers, Bastiaan Bakker LifeLine Networks bv > -- > GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc > <rei_> Derick, while ($xml) $ass->get_new_ideas(); > <[James]> Markus: IE on_user_fart()???? > -- People doesn't seem to like the new XHTML2 specs :) --