authentik proxy: Header Accept-Encoding of text/event-stream gets changed to gzip in chrome / edge

[troem]

Hallo, first of all thank you for your great work - I really appreciate authentik and its great functionalities and its simple interface!

I am using the authentik proxy for "openHAB". With firefox it is working fine in all cases. However: With chrome/edge the eventstream does not work, because the content-encoding is wrongly changed to "gzip". I tried to set a custom header in authentik via property-mapping without success. My current workaround is to use the chrome extension "ModHeader".
Is there any way, to change/adopt this header / behavior of the authentik proxy, to have the header "Accept-Encoding" of "text/event-stream" as it is used from openHAB without getting touched by authentik? And is this possible, to limit that to the "/rest/events/states" of the proxy?

Thank you for any help!

[troem]

Hello, I did an small PoC and created an authentik proxy for the public openHAB demo page: https://demo.openhab.org/overview
Via the openHAB demo the above mentioned challenge is reproducible. e.g.: if you click in the demo on "Temperatures" you cannot see any values, just boxes without data. The values are seen without authentik and the reason is the header "Accept-Encoding" in the "/rest/events/states". Is there any way to change this e.g. via request variable and a user-defined call for e.g. s.headers.update({'Accept-Encoding': 'text/event-stream'})

Thank you for any help!