The variable backend_response is not usable when custom-logging OIDC token and userinfo responses. However it can be used when custom-logging openid-configuration and JWKS responses.
To Reproduce
Steps to reproduce the behavior:
Which Couper version? Run couper version or docker run coupergateway/couper version
$ couper version
0 2024-02-01 dev
go version go1.20.6 linux/amd64
Provide your configuration file *.hcl. Remove sensitive data.
Here you see in the log entries for the openid-configuration and the jwks requests, that, in addition to foo:bar, there is also the br entry representing the JSON response body.
In the log entries for the token and userinfo requests only foo:bar is logged, no br entry.
And: the logged request name for token and userinfo requests is <nil>.
Expected behavior
I expect that the response received from the token and userinfo requests can also be custom-logged.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Describe the bug
The variable
backend_response
is not usable when custom-logging OIDC token and userinfo responses. However it can be used when custom-logging openid-configuration and JWKS responses.To Reproduce Steps to reproduce the behavior:
couper version
ordocker run coupergateway/couper version
*.hcl
. Remove sensitive data.Provide a
curl
call for reproduction 3.1 You may use your browsers developer console and hitcopy as curl
.See an error response or error log.
Here you see in the log entries for the openid-configuration and the jwks requests, that, in addition to
foo:bar
, there is also thebr
entry representing the JSON response body. In the log entries for the token and userinfo requests onlyfoo:bar
is logged, nobr
entry.And: the logged request name for token and userinfo requests is
<nil>
.Expected behavior
I expect that the response received from the token and userinfo requests can also be custom-logged.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.