You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are three problems on the authorization error page when OIDCUnAutzAction auth setting.
I think these are probably bugs, can you comment? (This issue seems to be similar to Issue #467)
Problems:
The HTTP header and body part when the authorization error occurs is duplicated(mod_auth_openidc authorization error 200 page + apache 401 error page), and the Content-length is only the size of the first half of the content.(See Network capture)
The HTTP header shows 200 status, but Apache's access_log shows 401 status, and the content is outputted to pages with 401 error.(See access_log and Network capture)
Since the Content-length does not match the actual body size, the meta-tag location change may not work properly when passing through some load balancers (ELB) using Chrome etc.
There are three problems on the authorization error page when
OIDCUnAutzAction auth
setting.I think these are probably bugs, can you comment? (This issue seems to be similar to Issue #467)
Problems:
The HTTP header and body part when the authorization error occurs is duplicated(mod_auth_openidc authorization error 200 page + apache 401 error page), and the Content-length is only the size of the first half of the content.(See Network capture)
The HTTP header shows 200 status, but Apache's access_log shows 401 status, and the content is outputted to pages with 401 error.(See access_log and Network capture)
Since the Content-length does not match the actual body size, the meta-tag location change may not work properly when passing through some load balancers (ELB) using Chrome etc.
My environments:
How to reproduce:
Configuration:
access_log(when authorization error):
Network capture(when authorization error):
The text was updated successfully, but these errors were encountered: