Hallo everybody

I was away for a while, so I'd like to answer some of the pending posts
here.

- error 0 in log files (from HKS): this usually means a time-out during
the data transfer or similar. Unless you get a lot of them it is not
really serious.

- failed connections to back-ends and kill_be (Joe Gooch): connecting to
a back-end is the cheapest check, certainly cheaper than reading a page
and checking on its status. I fully agree that killing a back-end should
be logged - we'll add that to the next release.

- error in the code when rewriting Location header (SBR/Andrew): it is
indeed a bug and we'll fix it in the next release.

- error in ClientCert (Ravindra Ghanate): the correc t syntax would be
"ClientCert 1 9" - see the manual for details.

- session tracking on parameter (Ron Bloom): in the path /a;b/c the
element "a;b" is considered a single path element, with the "b" part
usually reserved for OS-specific stuff (such as file version). Have a
look at RFC 2396 for all the gory details. I think we should stick to
the accepted standards and use "?" as a separator between the path and
the query parameters.

- logging of failed connection to a back-end (Jon Garvin): Pound should
indeed log this - we'll add that to the next version.

- autoconf dependencies (Thilo Bangert): we'll add -without-pcre,
--without-hoard, --without-tcmalloc in the next version.

- case-insensitive URL matching: quite frankly, given that you can do in
the regular expression itself, I don't see the benefit of adding a
configuration flag for that.

Hope this covers it all - let me know if I missed anything.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904


--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.

Reply via email to