rgw/logging: use trans_id for standard access log record

In standard mode, the access log record was using s->req_id for the
request ID field. The correct field is s->trans_id, which matches the
x-amz-request-id returned in the S3 response. This is consistent with
how all other RGW response code uses trans_id.

Fixes: http://tracker.ceph.com/issues/75416
Signed-off-by: cheese-cakee <farzanaman99@gmail.com>

diff --git a/src/rgw/rgw_bucket_logging.cc b/src/rgw/rgw_bucket_logging.cc
index bfb76a46c77d8e4adfa1638976e0eec0751a0fc3..5d29e17ce2101d9db1ee4838f92ab9a42acf707a 100644 (file)
--- a/src/rgw/rgw_bucket_logging.cc
+++ b/src/rgw/rgw_bucket_logging.cc
@@ -585,7 +585,7 @@ int log_record(rgw::sal::Driver* driver,
         t,
         s->info.env->get("REMOTE_ADDR", "-"),
         dash_if_empty(user_or_account),
-        dash_if_empty(s->req_id),
+        dash_if_empty(s->trans_id),
         op_name,
         dash_if_empty_or_null(obj, obj->get_name()),
         s->info.method,