A warning message would be nice, so users can step on it. +1 :) Luis.
On Thu, 12 Jul 2018 at 23:03, Luca Toscano <toscano.l...@gmail.com> wrote: > Hi! > > 2018-07-12 20:50 GMT+02:00 <jaillet...@apache.org>: > >> Author: jailletc36 >> Date: Thu Jul 12 18:50:24 2018 >> New Revision: 1835761 >> >> URL: http://svn.apache.org/viewvc?rev=1835761&view=rev >> Log: >> Explain the limitation of <IfFile> with a filename with surrounding >> quotes in 2.4.34. >> >> Modified: >> httpd/httpd/trunk/docs/manual/mod/core.xml >> >> Modified: httpd/httpd/trunk/docs/manual/mod/core.xml >> URL: >> http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/core.xml?rev=1835761&r1=1835760&r2=1835761&view=diff >> >> ============================================================================== >> --- httpd/httpd/trunk/docs/manual/mod/core.xml (original) >> +++ httpd/httpd/trunk/docs/manual/mod/core.xml Thu Jul 12 18:50:24 2018 >> @@ -2341,7 +2341,13 @@ if file exists at startup</description> >> the path will be checked relative to the compiled-in server root or >> the server root passed in on the command line via the <code>-d</code> >> parameter.</p> >> - >> + >> + <note type="warning"><title>Warning</title> >> + In 2.4.34, it is not possible to specify a <var>filename</var> >> + with surrounding quotes. This would generate a parsing error at >> start-up. >> + The main impact is that filenames with spaces can't be used. >> + This behavior is fixed in 2.4.35.</note> >> + >> </usage> >> </directivesynopsis> >> > > In this case, it is better to add a warning box or add this note to > compatibility? Genuine question, I am always struggling to find the best > compromise :) > > Luca >
