Could someone please remind me why --with-capath is mandatory when
--enable-ssl is used? The default is only useful if you actually
use --with-ssl=some/path. I have a patch that changes the default to
$sysconfdir/certs, but in the long run I think this should be something
configured through the
* Swapan Gupta [EMAIL PROTECTED] wrote:
I am trying to use the function apr_table_setn for redirecting to a URL.
The following is the function call that I am using.
apr_table_setn( m_pReqRec-headers_out, (const char *)Location,
apr_pstrdup(m_pReqRec-pool, URL ));
But somehow I am not
But somehow I am not properly getting redirected. What I am getting is a
blank page instead of the page I am trying to redirect to.
Any ideas why this could be happening? Do I need to do a configuration
setting for this redirect to function properly or is there something
wrong with the way
amit athavale wrote:
But somehow I am not properly getting redirected. What I am getting is a
blank page instead of the page I am trying to redirect to.
Any ideas why this could be happening? Do I need to do a configuration
setting for this redirect to function properly or is there something
wrong
* Eduardo Franco [EMAIL PROTECTED] wrote:
amit athavale wrote:
But somehow I am not properly getting redirected. What I am getting is
ablank page instead of the page I am trying to redirect to.
Any ideas why this could be happening? Do I need to do a configuration
setting for this redirect
Jeff Trawick wrote:
Ben Laurie wrote:
If it does nothing unless a file is specified, why not enable by default?
to avoid silent growth in the set of code built into somebody's
server... when does somebody have to add --disable-foo to create a
build compatible with what they had with the
Colm MacCarthaigh wrote:
On Mon, Dec 29, 2003 at 01:39:28PM +, Ben Laurie wrote:
So, I've written a forensic logging module. What this does is log the
request as soon as all the headers have been read, then log again when
its complete. Any request that doesn't complete should be viewed
Colm MacCarthaigh wrote:
On Mon, Dec 29, 2003 at 01:39:28PM +, Ben Laurie wrote:
So, I've written a forensic logging module. What this does is log the
request as soon as all the headers have been read, then log again when
its complete. Any request that doesn't complete should be
Thanks.
The problem is resolved. The response status was not set properly.
-Original Message-
From: André Malo [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 30, 2003 5:03 PM
To: [EMAIL PROTECTED]
Subject: Re: Problem in URL redirect
* Eduardo Franco [EMAIL PROTECTED] wrote:
amit
* David Reid [EMAIL PROTECTED] wrote:
Colm MacCarthaigh wrote:
On Mon, Dec 29, 2003 at 01:39:28PM +, Ben Laurie wrote:
So, I've written a forensic logging module. What this does is log the
request as soon as all the headers have been read, then log again when
its complete.
David Reid wrote:
Colm MacCarthaigh wrote:
On Mon, Dec 29, 2003 at 01:39:28PM +, Ben Laurie wrote:
So, I've written a forensic logging module. What this does is log the
request as soon as all the headers have been read, then log again when
its complete. Any request that doesn't complete
But somehow I am not properly getting redirected. What I am getting is
ablank page instead of the page I am trying to redirect to.
Any ideas why this could be happening? Do I need to do a configuration
setting for this redirect to function properly or is there something
wrong with the way
On Tue, Dec 30, 2003 at 11:49:37AM +, Ben Laurie wrote:
Could the forensic_id be tied in with mod_unique_id? It seems confusing
to have two different methods to generate unique id's for requests. Also
with unique_id, I can see it being useful to make CGI's aware of their
tracking code via
Ben Laurie wrote:
Bill Stoddard wrote:
Ben Laurie wrote:
If it does nothing unless a file is specified, why not enable by
default?
Like Jeff, I am more interested in this for debugging process crashes
that are not necessarily related to attacks. Might be useful to enable
this function by
Bill Stoddard wrote:
Ben Laurie wrote:
Bill Stoddard wrote:
Ben Laurie wrote:
If it does nothing unless a file is specified, why not enable by
default?
Like Jeff, I am more interested in this for debugging process crashes
that are not necessarily related to attacks. Might be useful to
For review - or shall I just commit?
Cheers,
Ben.
--
http://www.apache-ssl.org/ben.html http://www.thebunker.net/
There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit. - Robert Woodruff
/*
Bill Stoddard wrote:
Bill Stoddard wrote:
Ben Laurie wrote:
Bill Stoddard wrote:
Ben Laurie wrote:
If it does nothing unless a file is specified, why not enable by
default?
Like Jeff, I am more interested in this for debugging process
crashes that are not necessarily related to attacks.
Colm MacCarthaigh wrote:
On Tue, Dec 30, 2003 at 11:49:37AM +, Ben Laurie wrote:
Could the forensic_id be tied in with mod_unique_id? It seems confusing
to have two different methods to generate unique id's for requests. Also
with unique_id, I can see it being useful to make CGI's aware of
On Tue, 2003-12-30 at 19:52, Ben Laurie wrote:
I realise that having the value of getpid() and time() to hand is useful
for forensic purposes, but a getpid():time():next_id++ will result in
duplicates accross even small clusters.
Ah, I see :-) does mod_unique_id handle that?
/me sees a
On Tue, Dec 30, 2003 at 06:52:07PM +, Ben Laurie wrote:
I realise that having the value of getpid() and time() to hand is useful
for forensic purposes, but a getpid():time():next_id++ will result in
duplicates accross even small clusters.
Ah, I see :-) does mod_unique_id handle that?
It
20 matches
Mail list logo
