Currently we don't log request and response headers for Linksharing, unlike Gateway-MT. That can make debugging a little more difficult. For example, we don't know which range header the client may have sent, which could be helpful for debugging a ranged request.
Acceptance Criteria
I can find request and response headers in the log output for Linksharing requests, and in the same format as Gateway-MT currently logs them.
Any known sensitive headers are redacted and not logged, e.g. for Gateway-MT we replace the Authorization header value with [...].
Goal
Currently we don't log request and response headers for Linksharing, unlike Gateway-MT. That can make debugging a little more difficult. For example, we don't know which range header the client may have sent, which could be helpful for debugging a ranged request.
Acceptance Criteria
I can find request and response headers in the log output for Linksharing requests, and in the same format as Gateway-MT currently logs them.
Any known sensitive headers are redacted and not logged, e.g. for Gateway-MT we replace the Authorization header value with
[...]
.Notes
Logging middleware for Gateway-MT can be found here: https://github.com/storj/gateway-mt/blob/main/pkg/server/middleware/log.go