Re: 1.3 now blocking on path escaping in httpd operational logging

* kfogel@collab.net wrote:

> > > As I was trying to make clear in IRC yesterday, UTF-8 isn't an
> > > option. httpd (via ap_escape_logitem function) will convert the
> > > high-bit values via the c2x() function - which will print the hex
> > > value anyway (%xx).

Ahem. No.

> Okay. In other words, httpd essentially cannot log events about local
> (server) paths in a perfectly parseable way. Furthermore, the
> escaping that httpd enforces actually uses *two* different escape
> codes: \ for some things, and % for others. But only one of the
> sequences escapes itself; the other does not, and cannot be
> distinguished from that escape sequence simply appearing in the
> original string.

Only \xx is used. Well, c2x is utilized, but the logging escaper replaces
the % with an x and precedes the whole sequence with an \ (-> \xhh).
See ap_escape_logitem in server/util.c.

nd

-- 
"Solides und umfangreiches Buch"
                                          -- aus einer Rezension
<http://pub.perlig.de/books.html#apache2>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org