hugh williams <hughw@xxxxxxxxxxxxxxxx> writes: > My question still remains - what changed in Apache that a construct it > formerly parsed one way is now treated differently? Or not so much > what changed, but why? Why does Apache now "care" what is inside an > exec cmd' string? Even in 1.3, mod_include interpreted $ in an exec cmd string as a variable substitution, and the doc warned that to include a literal $, it needed to be quoted with a backslash. The implementation probably changed in a way that made it less forgiving of having a $ not followed by the name of an existing variable, but that was never actually legal. Dan --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|