Doubtfully. They've been aware of that for a long time: http://httpd.apache.org/docs/2.0/misc/known_client_problems.html
In either case, Peruser/Perchild/Metux have nothing to do with the request data itself asides from the Host header identifying which vhost to look at.
-- Tino Didriksen Leen Besselink wrote:
Hi,
Today I was reading some code of an other server-application (Perlbal by Danga).
And I came across this note in Perlbal::Socket:
# some browsers send an extra \r\n after their POST bodies that isn't
# in their content-length.
Could that be the reason for the problems peruser (and also metuxmpm) has/had ?
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
