`user_claim` and `realm_claim` null if upstream returns 405

[wodzuu]

Observed with version 1.6.1

To reproduce:

1. Make upstream server return 405 for the test http call
2. Make the test call with JWT bearer token

Expected:

The call is logged in the clickhouse log table and is properly annotated with user_claim and realm_claim extracted from the token

Actual:

Both user_claim and realm_claim are null

[ethlo]

The reason is not the upstream response code, but the fact that the request is not read by the upstream server (application).
The 405 is likely nginx not knowing what to do with a POST for an error page.