From 6c41ffd9bc51a95f7aa200dbb38604aac9db5a9f Mon Sep 17 00:00:00 2001 From: Kota Tsuyuzaki Date: Wed, 4 Mar 2015 17:55:52 -0800 Subject: [PATCH] Update doc about force_swift_request_proxy_log Change-Id: Ibd227183d5e98ec0ffcafee8f4ddf4e8f941b3e4 --- etc/proxy-server.conf-sample | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/etc/proxy-server.conf-sample b/etc/proxy-server.conf-sample index ae397d80..663407ea 100644 --- a/etc/proxy-server.conf-sample +++ b/etc/proxy-server.conf-sample @@ -96,8 +96,14 @@ use = egg:swift3#swift3 # If you set this to false, Swift3 returns all buckets. # check_bucket_owner = false # -# If set to 'true', proxy-logging output access log from Swift3 to -# proxy-server. +# In default, Swift reports only S3 style access log. +# (e.g. PUT /bucket/object) If set force_swift_request_proxy_log +# to be 'true', Swift will become to output Swift style log +# (e.g. PUT /v1/account/container/object) in addition to S3 style log. +# Note that they will be reported twice (i.e. Swift3 doesn't care about +# the duplication) and Swift style log will includes also various subrequests +# to achieve S3 compatibilities when force_swift_request_proxy_log is set to +# 'true' # force_swift_request_proxy_log = false [filter:catch_errors]