On Sat, Jan 30, 2010 at 2:04 AM, Stefan Fritsch wrote:
> The recommended setup is to map separate URLs for DAV and script
> execution to the content. It has been like this since at least 2.0.
>
> The patch intentionally breaks existing configs that rely on the
> ability to use the same URLs for DA
On 30.01.2010 19:40, Stefan Fritsch wrote:
A related question: I want to introduce a directive to set variables
that are expanded during config file parsing, just like environment
variables are. The problem I want to solve is that environment variables
cannot be changed during graceful restart. W
On Sat, 30 Jan 2010, Graham Leggett wrote:
On 30 Jan 2010, at 12:04 PM, Stefan Fritsch wrote:
I don't follow how this makes it easier to use the recommended setup?
In your example config, you defined /dav as being handled by mod_dav, and
then you defined a FilesMatch (as I recall) that defined
On Sat, 30 Jan 2010, Jeff Trawick wrote:
On Sat, Jan 30, 2010 at 8:52 AM, Dan Poirier wrote:
I'm just curious, why use Define with ! rather than creating a new
Undefine directive?
same question here
No particular reason except the similarity to "". I will
change it to Undefine.
A relat
On 30 Jan 2010, at 3:55 PM, Jeff Trawick wrote:
I'm just curious, why use Define with ! rather than creating a new
Undefine directive?
same question here
Of course "Define !FOO" has some similarities with ","
but it is even more unsatisfying aesthetically IMHO.
+1.
Regards,
Graham
--
On 30 Jan 2010, at 12:04 PM, Stefan Fritsch wrote:
The recommended setup is to map separate URLs for DAV and script
execution to the content. It has been like this since at least 2.0.
The patch intentionally breaks existing configs that rely on the
ability to use the same URLs for DAV and scrip
On Sat, Jan 30, 2010 at 8:52 AM, Dan Poirier wrote:
> I'm just curious, why use Define with ! rather than creating a new
> Undefine directive?
same question here
Of course "Define !FOO" has some similarities with ","
but it is even more unsatisfying aesthetically IMHO.
I'm just curious, why use Define with ! rather than creating a new
Undefine directive?
Dan
Just a reminder; Intention is to release 1.3.42 on Tuesday. If anyone
has strong feelings, make them known :-) Nóirín has kindly translated
the announcement into English;
http://people.apache.org/~noirin/Announcement1.3.txt
2010/1/27 Colm MacCárthaigh :
> 2010/1/27 Colm MacCárthaigh :
>> On Wed,
On Fri, Jan 29, 2010 at 3:25 AM, Tatsuki Sugiura wrote:
> Hello all,
>
> I found a problem that mod_fcgi makes segmentation fault
> when FastCGI process returns empty outout. It's caused
> with missing to check end of brigade when parsing CGI
> response header.
>
> I worte a patch to fix this, and
On Saturday 30 January 2010, Roy T. Fielding wrote:
> > */
> > if (!conf->provider->repos->handle_get) {
> > +if (r->finfo.filetype != APR_DIR)
> > +r->handler = "none";
> > return DECLINED;
> > }
> > }
>
> It looks to me like th
11 matches
Mail list logo