markusmueller opened a new issue, #11492:
URL: https://github.com/apache/apisix/issues/11492

   ### Current Behavior
   
   Using Firefox version >= 128.0 the `/logout` path provided by the 
openid-connect plugin is not redirecting to the configured IDP for logout but 
instead returning a 1x1 pixel image.
   
   Root Cause:
   Firefox Version 128.0 changed the 
[`network.http.accept`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_negotiation/List_of_default_Accept_values)
 default value also adding `image/png`. 
   
   This is causing 
[lua-resty-openidc](https://github.com/dgitsystems/lua-resty-openidc/tree/master)
 used by the openid-connect plugin to return the image.
   
   There is already a discussion on 
[lua-resty-openidc](https://github.com/zmartzone/lua-resty-openidc/issues/521). 
   
   Once the issue is resolved upstream the dependency should be updated.
   
   A possible workaround in the meantime is patching the openid-connect plugin 
and overwriting the `Accept` header for the `/logout` path in 
[openid-connect.lua](https://github.com/apache/apisix/blob/4c87264d0d18efafb1abc3ebad4fd88cbd49f5a9/apisix/plugins/openid-connect.lua#L509):
   
   ` ngx.req.set_header("Accept", "text/html")`
   
   ### Expected Behavior
   
   Using Firefox v 128.0 the path `/logout`  will redirect to the configured 
IDP for logout. 
   
   ### Error Logs
   
   _No response_
   
   ### Steps to Reproduce
   
   Configure Apisix openid-connect plugin with logout and hit `/logout` using 
Firefox version >= 128.0.
   
   ### Environment
   
   - APISIX version (run `apisix version`):
   - Operating system (run `uname -a`):
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to