#22904 [Bgs->WFx]: sybase_magic_quotes does stuff with '\0' string

From: Date: Wed, 23 Apr 2003 20:40:31 +0000
Subject: #22904 [Bgs->WFx]: sybase_magic_quotes does stuff with '\0' string
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-38233@lists.php.net to get a copy of this message
ID: 22904 Updated by: momo@php.net Reported By: momo@php.net -Status: Bogus +Status: Wont fix Bug Type: Sybase-ct (ctlib) related Operating System: linux RH7.2 PHP Version: 4.3.2RC1 New Comment: as i answerd ilia, if the stripslashes have to recover the string as it was before addslashes'ing so it fails. changing this behavior mean changing all this "magic" thing so won't fix is the correct status. Previous Comments: ------------------------------------------------------------------------ [2003-04-23 04:32:05] sniper@php.net I can't see any bug here.. ------------------------------------------------------------------------ [2003-04-01 07:24:16] momo@php.net i revert the fix, coz some unexpected effects. i'll try later. ------------------------------------------------------------------------ [2003-03-31 06:31:00] momo@php.net if the stripslashes have to recover the string as it was before addslashes'ing so it fails. all this code looks to me too disordered. for example, into the sybase stripslashes there is the code: ---- if (*t == '\'') { if ((l > 0) && (t[1] == '\'')) { t++; if (len != NULL) { (*len)--; } l--; } *s++ = *t++; --- but this code have nothing with slashes at all! i'll try to learn the subject when i'll find some time for it and do some order. ------------------------------------------------------------------------ [2003-03-27 09:06:47] iliaa@php.net Is this even a bug? It seems to me the code follows the 'proper' behaviour for sybase_magic_quotes, no? ------------------------------------------------------------------------ [2003-03-27 03:48:52] wez@php.net Nothing to do with fwrite ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/22904 -- Edit this bug report at http://bugs.php.net/?id=22904&edit=1

« previous php.bugs (#38233) next »