On Sat, May 05, 2007 at 11:42:23AM +0200, Joachim Zobel wrote:
I am currently trying to track down a glibc memory corruption. To do
this I tried the following (see below). This is done on prefork.
ap_log_perror(APLOG_MARK, APLOG_DEBUG, 0, p_cur,
xml2_free will free
Joachim Zobel wrote:
Hi.
I am currently trying to track down a glibc memory corruption. To do
this I tried the following (see below). This is done on prefork.
However no logging takes place. Is there something obvious I am doing
wrong?
Thx,
Joachim
Thiabut,
As far as I know, URI escaping functions escape all non-alpha numberics
which are not in the following set of characters: {'-', '_', ':', '/', '?',
'=', '', '#', '.'} (there may be others I can't think of right now). If a
character is in that set of characters, the URI remains legal
Am Samstag, den 05.05.2007, 13:44 -0400 schrieb Tom Donovan:
static apr_pool_t *p_cur = NULL;
void xml2_set_current_pool(apr_pool_t * p)
{
// Needed for free-logging
p_cur = p;
}
static void xml2_child_init(apr_pool_t * p, server_rec * s)
{
Thibut,
Point taken. I didn't have any trouble with ap_escape_uri, but then
again I'm not testing on Debian.
I fear the problem is that the ap_escape_uri(...) function has been
turned into a macro for the ap_os_escape_path(...) function (as you said
before). It seems as though the
I'd be so much happier if I had unit tests, but it's tricky since
everything's static. My best idea is to have an #ifdef TESTING
section in my code that has a main() in it that runs the tests (of
course this means actually *understanding* the lovely makefile
goodness I copied from Josh
On 05.05.2007 04:25, Brian Hayward wrote:
BTW, I did test my patch when 1 host was down in a balancer
configuration. It still seemed to work well.
I would think so. My point was more about that with this setting the
response times of your reverse proxy will increase as it may try all failed
I am leaning towards changing all the userdata types (request_rec,
server_rec, conn_rec, apr_table_t) in mod_wombat to have anonymous
metatables rather than the current setup where they share a metatable.
The benefit of going to a per-instance metatable is that we can curry
the relevant
