Well, my patch is at the end, leaving the rm in place. However, I could
examine looking at using slibclean (shared library clean) - which is the
program to remove outstanding (loaded, but not active) shared library code.
And - thinking through - if the remove is not done, and the .so file is not
I see I did not read far enough - as you found the reference to slibclean.
In it's defense I expect the IBM install program is using slibclean during
it's installation of files - or, the files are being moved to something
like /usr/lpp/lpp.name/save (it has been a long long time since I have
Trying to get my 2.4.x reviews in.
Maybe I'm misunderstanding the change, but wasn't the previous
behavior more desirable?
If the entry were within its expiry, those same headers wouldn't have
been sent to the client (well, none but the first who filled in the
cache). Why should it act
I don't want to churn in SVN too much, does anyone have an issue with
dropping the context info stuff for the regex case completely?
On Mon, Mar 31, 2014 at 1:49 PM, Eric Covener cove...@gmail.com wrote:
So you suggest to remove ap_set_context_info() from the AliasMatch handling?
Yes, I just
!me.
On May 5, 2014, at 9:34 AM, Eric Covener cove...@gmail.com wrote:
I don't want to churn in SVN too much, does anyone have an issue with
dropping the context info stuff for the regex case completely?
On Mon, Mar 31, 2014 at 1:49 PM, Eric Covener cove...@gmail.com wrote:
So you suggest
On Mon, May 5, 2014 at 10:14 AM, traw...@apache.org wrote:
Author: trawick
Date: Mon May 5 14:14:53 2014
New Revision: 1592537
URL: http://svn.apache.org/r1592537
Log:
$ ./test/readbody.sh httpd scgi tcp 1 100 21 | egrep '(Document
Length|Failed requests|Requests per second)'
On 05.05.2014 15:34, Eric Covener wrote:
I don't want to churn in SVN too much, does anyone have an issue with
dropping the context info stuff for the regex case completely?
Thanks for asking again and agreed here.
Regards,
Rainer
On Mon, Mar 31, 2014 at 1:49 PM, Eric Covener
Hi,
why not having SCGI_DEFAULT_PORT in a .h file, just as AJP13_DEF_PORT?
This would avoid using SCGI_DEFAULT_PORT in one place and 4000 in another.
Moreover, this could be renamed as SCGI_DEF_PORT to be consistent with AJP.
Just my 2 cents.
CJ
Le 05/05/2014 16:02, traw...@apache.org a
On Mon, May 5, 2014 at 2:59 PM, Marion Christophe JAILLET
christophe.jail...@wanadoo.fr wrote:
Hi,
why not having SCGI_DEFAULT_PORT in a .h file, just as AJP13_DEF_PORT?
This would avoid using SCGI_DEFAULT_PORT in one place and 4000 in another.
Moreover, this could be renamed as
Moreover,
all mod_proxy_something that do not append the port when the default is
used are built this way:
static int FCT_canon(request_rec *r, char *url)
{
[...]
apr_port_t port, def_port;
[...]
if (port != def_port)
apr_snprintf(sport, sizeof(sport), :%d, port);
Thanks :)
The comment also answer a question I had: Where does this default 4000
comes from?
/** @} */
missing ?
CJ
Le 05/05/2014 21:26, traw...@apache.org a écrit :
Author: trawick
Added: httpd/httpd/trunk/modules/proxy/scgi.h
URL:
[Posting separately to both dev and users to see if anyone on either side sees
value in getting this committed.]
About a year ago, I had an idea for a new type of RewriteMap that would fill an
important need for a few particular use cases that we have [1]. While we were
at ApacheCon in Denver,
On Mon, May 5, 2014 at 3:43 PM, Marion Christophe JAILLET
christophe.jail...@wanadoo.fr wrote:
Thanks :)
The comment also answer a question I had: Where does this default 4000
comes from?
/** @} */
missing ?
r1592632
Thanks!
CJ
Le 05/05/2014 21:26, traw...@apache.org a écrit :
13 matches
Mail list logo
