https://bz.apache.org/bugzilla/show_bug.cgi?id=65546
--- Comment #4 from Christophe JAILLET <christophe.jail...@wanadoo.fr> --- (In reply to Bruce Momjian from comment #2) > Seems you can just add any key name instead of "text"? Correct. I just proposed "text" that looks like a somewhat logical key name :) > How do you handle text with single/double quotes in them? > I guess you can use double quotes for text > with single quotes, and single quotes for text with double quotes, but how > would you handle text with both? Just escape the quote within the text (i.e. \" or \' or \`) > I assumed #comment operated just like HTML comments and went to the end of > the --> block. I do think the feature is useful in allowing comments to be > used without sending them to the client. Yes, it behaves mostly the same. Everything up to the closing --> is just ignored In fact, there is a special test (see [1]) that tries to spot obvious configuration issues. All mod_include elements expect parameters passed as key or key=value. If value has some spaces, there must be some surrounding " or ' or `. A key starting with a quote is not possible and is likely a missing key in fact. It is what you have hit with the 'comment'. > What I ended up doing was to add > an underscore before a single or double quote that had a space before it, > but that is kind of odd. I works for the same reason <!-- comment blah blah --> works. The parser sees your _"some text" as just a (normal) key because it does not start with a quote. [1]: http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/filters/mod_include.c?view=markup#l3203 -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
