You might also want to check your syslog to see if suhosin is generating errors
Normally this is /var/log/messages
but might be
/var/log/system.log on your Mac
You might also want to check your syslog to see if suhosin is generating errors
Normally this is /var/log/messages
but might be
/var/log/system.log on your Mac
The suhosin line was not in the php.ini file, so I added it and restarted apache. Does not seem to have had any effect
I can not find any suhosin errors, but the file certainly contains error. See:
http://www.altikost.no/system.txt
...don't know if anything is of interest relating to this matter though....
k,
I have been looking in all the wrong places for the problem :)
Its actually cause by some security code in application_top.php
change the 43 to something like 199 and you should be OK.PHP Code:
if (isset($_GET[$key]) && strlen($_GET[$key]) > 43) {
$contaminated = true;
break;
}
This is on our workboard to address for v1.6
Fantastic! Seems like the site is back on track :)
Should I keep the sesskey at 255 or change it back to 128?
I would leave it at 255.
While it may seem excessive at the moment, 128 would have seemed excessive a year or 2 ago
Bookmarks