Exactly, most of my servers do not give this warning at all.
This one does, and I can't see or edit httpd.conf unfortunately. I think its a change in Apache from version 1.3.20 to 1.3.22
I found this in the 1.3.22 changelog
The main new features in 1.3.22 (compared to 1.3.20) are: ... The server will now display a warning if line-end comments (#) are found in the configuration file. Not all directives are able to handle comments on the same line ...
But there is no talk about a disable for it, and if I will be able to use such a directive in HTACCESS vs httpd.conf
I suspect that your server which is behaving differently has its LogLevel set to warn, rather than error. LogLevel is part of the Apache core, but is accessible only in server and virtual host config. :(
...Pretty strange that it issues a warning even though the script and the directives that the script writes demonstrably work fine... I've got too many dead spiders lying around here to believe that this system isn't working. :)
I guess you'll have to put up with the error entries, or add the \n as you stated.