swift/test
Clay Gerrard 5af7719ef3 Support swift.proxy_logging_status in request env
When logging a request, if the request environ has a
swift.proxy_logging_status item then use its value for the log
message status int.

The swift.proxy_logging_status hint may be used by other middlewares
when the desired logged status is different from the wire_status_int.

If the proxy_logging middleware detects a client disconnect then any
swift.proxy_logging_status item is ignored and a 499 status int is
logged, as per current behaviour. i.e.:

  * client disconnect overrides swift.proxy_logging_status and the
    response status
  * swift.proxy_logging_status overrides the response status

If the proxy_logging middleware catches an exception then the logged
status int will be 500 regardless of any swift.proxy_logging_status
item.

Co-Authored-By: Alistair Coles <alistairncoles@gmail.com>
Change-Id: I9b5cc6d5fb69a2957b8c4846ce1feed8c115e6b6
2023-12-20 17:31:06 +00:00
..
cors s3api: Allow CORS preflights for pre-signed URLs 2021-07-14 10:52:12 -07:00
functional Include accept-ranges header in s3api response 2023-10-13 16:39:09 +00:00
probe proxy: remove x-backend-record-type=shard in object listing 2023-12-11 14:18:20 +00:00
s3api s3api: Add basic GET object-lock support 2023-10-05 16:38:35 +11:00
unit Support swift.proxy_logging_status in request env 2023-12-20 17:31:06 +00:00
__init__.py Clean up some cruft 2023-01-19 12:56:08 -08:00
debug_logger.py Merge "proxy: Get rid of MetricsPrefixLoggerAdapter" 2023-09-11 05:10:00 +00:00
sample.conf fix s3api functional tests 2020-05-15 22:38:04 -07:00