As now it handles these strings it gets the same:
name="whatever,this,might,be";name2="value2"
name="whatever,this,might,be",name2="value2"
How can this affect modsecurity at all
Forgive me my ignorance, but I do not see any handling of " chars.
your strings should now resu
This patch was supposed to make it RFC compliant.
Can you please point me the part in the RFC 2965
which now isn't implemented correctly?
As now it handles these strings it gets the same:
name="whatever,this,might,be";name2="value2"
name="whatever,this,might,be",name2="v
Hello Sebastian,
are you sure it works (e.g. the corresponding test succeed)?
Saturday, April 23, 2005, 10:52:29 AM, you wrote:
> I have bison 2.0 on my Gentoo Linux system an PHP's configure script
> gives a warning
>checking for bison version... invalid
>configure: WARNING: You wi
[EMAIL PROTECTED] php-5.1 % make install
Installing PHP CLI binary:/usr/local/php-5.1/bin/
Installing PHP CLI man page: /usr/local/php-5.1/man/man1/
Installing PEAR environment: /usr/local/php-5.1/lib/php/
[PEAR] Archive_Tar- installed: 1.1
[PEAR] Console_Getopt - installed: 1
I have bison 2.0 on my Gentoo Linux system an PHP's configure script
gives a warning
checking for bison version... invalid
configure: WARNING: You will need bison 1.28, 1.35, 1.75 or 1.875 if
you want to regenerate the Zend/PHP parsers (found 2.0).
but continues. As a result the bison
When I run PHPUnit2's own testsuite with a Release_TS build of
PHP 5.1.0-CVS I get a segfault (no backtrace since no symbols) on
shutdown.
When I run the same PHP sources with a Debug_TS build of PHP 5.1.0-CVS I
do not get a segfault but messages like this
[Sat Apr 23 10:31:14 2005] Scri
