https://bz.apache.org/bugzilla/show_bug.cgi?id=69549

--- Comment #2 from Philippe Cloutier <chea...@gmail.com> ---
Hey Lucien, thanks for your reply!

1. I had the same thought about missing backslashes. The thing is this
paragraph is about specifiers which sometimes produce no output. But some
specifiers always produce output, so they are not affected by this
complication. I assume that in the case of "pid" (and "tid"), there will always
be output. That being said, it may be clearer for readers to use backslashes
even if they are not required. It might even be more performant to do so. But
regarding client, I am afraid you are right; if not, then there is an
inconsistency with the second example.

2. Yes, "format string" refers to the variable part at the end of the
directive. The confusion is due to another sense used in that section, in the
largest table which uses "Format String" as its first heading and just after.
The section calls items like "%a" either "format string items" or just "format
strings". Moreover, in other pages (Log Files and mod_log_config), format
specifiers are called "percent-directives".

3. Indeed.

4. I do not see the use of "implicitly". I would ideally change:
« It can happen that some format string items do not produce output. For
example, the Referer header is only present if the log message is associated to
a request and the log message happens at a time when the Referer header has
already been read from the client. If no output is produced, the default
behavior is to delete everything from the preceding space character to the next
space character. This means the log line is implicitly divided into fields on
non-whitespace to whitespace transitions. If a format string item does not
produce output, the whole field is omitted. »
to:
« It can happen that some format string specifiers do not produce output. For
example, the Referer header is only present if the log message is associated to
a request and the log message happens at a time when the Referer header has
already been read from the client. If no output is produced, the default
behavior is to delete the field. Format strings are implicitly split into
fields. Spaces (which are not escaped) and explicit zero-width delimiters
separate fields. Implicit space separation occurs on non-whitespace to
whitespace transitions. »

5. Right, but none of the examples show how they are split into fields. If the
first example (simple) is used, there could be a table with 1 or 2 columns and
9 rows to show the contents of each field.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org

Reply via email to