You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Christophe Jaillet <ch...@wanadoo.fr> on 2018/07/10 20:24:15 UTC

2.4.34 issue with ?

Hi,

Should iffile.t be enabled for 2.4.34?

I guess so, but if extra.conf and iffile.t are tweaked to run with 
2.4.34+, there is a configuration parsing error at start-up because of:

       <IfFile "htdocs/apache/iffile/document">
         Header merge X-Out success5
       </IfFile>

the " seems to be a problem. After a quick look, I don't really see why.

CJ

Re: 2.4.34 issue with ?

Posted by Eric Covener <co...@gmail.com>.
Didn't even ring a bell but:
http://svn.apache.org/viewvc?view=revision&revision=1797844
On Tue, Jul 10, 2018 at 4:51 PM Eric Covener <co...@gmail.com> wrote:
>
> On Tue, Jul 10, 2018 at 4:24 PM Christophe Jaillet
> <ch...@wanadoo.fr> wrote:
> >
> > Hi,
> >
> > Should iffile.t be enabled for 2.4.34?
> >
> > I guess so, but if extra.conf and iffile.t are tweaked to run with
> > 2.4.34+, there is a configuration parsing error at start-up because of:
> >
> >        <IfFile "htdocs/apache/iffile/document">
> >          Header merge X-Out success5
> >        </IfFile>
> >
> > the " seems to be a problem. After a quick look, I don't really see why.
> >
>
> I see the same result, it only works if there's a single argument, so
> even <IfFile foo<SPACE>> fails.
> Old builds' IfDefine worked the same way from testing.
>
> Trunk has AP_INIT_RAW_ARGS instead of AP_INIT_TAKE1 which explains it
> but not sure how we got in this state.
>
>
>
> --
> Eric Covener
> covener@gmail.com



-- 
Eric Covener
covener@gmail.com

Re: 2.4.34 issue with ?

Posted by Eric Covener <co...@gmail.com>.
On Tue, Jul 10, 2018 at 4:24 PM Christophe Jaillet
<ch...@wanadoo.fr> wrote:
>
> Hi,
>
> Should iffile.t be enabled for 2.4.34?
>
> I guess so, but if extra.conf and iffile.t are tweaked to run with
> 2.4.34+, there is a configuration parsing error at start-up because of:
>
>        <IfFile "htdocs/apache/iffile/document">
>          Header merge X-Out success5
>        </IfFile>
>
> the " seems to be a problem. After a quick look, I don't really see why.
>

I see the same result, it only works if there's a single argument, so
even <IfFile foo<SPACE>> fails.
Old builds' IfDefine worked the same way from testing.

Trunk has AP_INIT_RAW_ARGS instead of AP_INIT_TAKE1 which explains it
but not sure how we got in this state.



-- 
Eric Covener
covener@gmail.com