<@U010F2N7G2X> <@U011D3UQKNY> Finally updated our ...
# contributors
r
@high-optician-2097 @magnificent-energy-493 Finally updated our PR: https://github.com/ory/oathkeeper/pull/916 Seems like most was already implemented through others, but it's still adding a few test cases. Yay, or nay?
m
Thanks for updating the PR! IMO this would be a good addition, but lets wait for Aeneas reply on gh! (might take a few days depending on what else is going on)
🙏 1
r
I see it got approved, is there anything else I need to do now? 😄
h
i need to click merge, my bad
ah no
the CI is failing
it looks like the grpc middleware tests are failing
the docker image scanners you can ignore
r
Not sure how to deal with timeouts?
h
That’s not a time out: https://github.com/ory/oathkeeper/actions/runs/4216722348/jobs/7348060071#step:9:172 It looks like you might run into a case where the tests use an empty subject. Since the code was changed, it’s possible that they now fail :)
r
any hint where to provide the subject line?
never used grpc before, i am a bit out of my depth 😃
h
not really 😞 I’d probably look at the failing test and revere engineer from there
r
I think the grpc test is fixed
but I think "now" there is another failure 😄
i think that's the original bug we reported with accept encoding being forwarded to the session store
full circle 😄
not really sure where to put it, so basically the problem is: • there's a config for forwarding to the session store • that config includes ForwardHTTPHeaders (which is a slice) • i think I need to strip
Accept-Encoding
from that list
but iterating over the slice seems kinda "icky"... as in, probably a performance penalty?
i think I would also need to refix this for "cookie"
lmk if you have any thoughts