httpAccessLogging: clarify that %I and %O are not supported format tokens

[riyaaroraa]

Please describe the problem you are having with the documentation. Is information missing, inaccurate, or unclear? Tell us about the context where you encountered the problem so we can understand how to address it.

Problem

The logFormat option table on this page does not list %I and %O as
supported tokens:
https://openliberty.io/docs/latest/access-logging.html

These tokens exist in Apache httpd's mod_log_config (bytes received / bytes
sent including headers), so customers commonly assume Liberty supports them
too. Configuring logFormat with %I or %O produces an FFDC:

java.lang.IllegalArgumentException: Config: invalid format segment: %I

This is expected behavior — %I/%O were never implemented in
AccessLogData — but the doc gap leads directly to support cases, since
customers can't tell if this is a bug or an unsupported feature.

Exact change requested

Add a row to the logFormat option table (or a note directly below it):

Token	Description
%I / %O	Not supported. These Apache httpd tokens for bytes received/sent including headers are not implemented in Liberty. Using them causes a startup FFDC (IllegalArgumentException: Config: invalid format segment: %I/%O). Use %b (response body bytes, excluding headers) as the nearest alternative.

Reference: TS022773695 / TS022451677

[ramkumar-k-9286]

Hi @riyaaroraa

Suggested changes have been added to the HTTP access logging page:

Draft Link: https://docs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/docs/latest/access-logging.html

Please review the same and add the Developer Reviewed label, if you are satisfied with the changes.

Regards,
Ramkumar.

[ramkumar-k-9286]

Published [26.0.0.9 release].