On 4/29/2015 11:54 PM, Jim Riggs wrote:
> [ Long message and proposal follows. Bear with me. There are a lot of words,
> but that is because we need a lot of help/input! ;-) ]
>
> So, this has come up in the past several times, and we discussed it again
> this year at ApacheCon: How do we get th
+1
By unbreaking configurations we are indeed changing behavior. This could
be an unexpected change for an admin during a minor upgrade but I weigh
that against the fact that directives enclosed by these matches may be
intended to add security/authorization/authentication which a badly
written link
On Thu, Apr 2, 2015 at 4:46 PM, William A. Rowe Jr.
wrote:
> On Tue, 31 Mar 2015 10:49:47 -0400
> Jim Jagielski wrote:
>
> > BTW: Would it make sense to consider a release of 2.4.13 in April
> > to coincide w/ ApacheCon?
>
> We've historically produced a release at the beginning of the con.
> It
On Thu, Apr 30, 2015 at 2:57 PM, Jim Riggs wrote:
>
> Thanks, Yann. I remember looking at this code before. The question remains,
> though: Is it currently "wrong"?
> Does it need to be "fixed", or was this distinction made intentionally?
> Is there a specific use case that requires the regex-mat
> On 28 Apr 2015, at 17:55, Yann Ylavic wrote:
>
> It seems that while is compared to ap_no2slash(r->uri),
> is matched against r->uri directly.
> That's probably the "issue".
>
> A possible fix (untested) could be:
>
> Index: server/request.c
> ===
On Wednesday, April 29, 2015, Jim Riggs mailto:apache-li...@riggs.me>> wrote:
Warn out from writing all of this and hopeful that someone other than me
actually cares, I wish you all well today/tonight!
*Worn* out, even! Boy, I was tired!
I'd been musing, coincidentally, about being able to run httpd as a FastCGI.
The motivation for this is a packaged webapp - Wordpress, say - that includes
.htaccess files in the deployed package.
Having the genuine Apache httpd able to serve the application and apply
.htaccess restrictions would
