-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Header.Authorization.Unparsed with empty authScheme cause code to hang forever #2742
Comments
/bounty $125 |
💎 $125 bounty • ZIOSteps to solve:
Thank you for contributing to zio/zio-http! Add a bounty • Share on socials
|
Not sure what you mean by that? The issue is fixed if I declare |
I'm kind of new here so it is quite overwhelming for me, and I do have many questions to ask, so I'm sorry about that. But can you explain me what exactly needs to be done? |
No offense but if I knew what needs to be done, I'd probably do it. I've provided a reproduction case, the goal is that the code in the reproduction case doesn't hang when you run it. Can you expand on what is unclear to you? |
I think it's my mistake that without prior knowledge I shouldn't have commented on this issue. sorry for the inconvenience. |
💡 @kyri-petrou submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
🎉🎈 @kyri-petrou has been awarded $125! 🎈🎊 |
Describe the bug
When using client code sending a request with an
Authorization
header with no scheme (Header.Authorization.Unparsed("", "some-key")
), the client code hangs forever.To Reproduce
Reproduction repository: https://github.com/gaeljw/ziohttp3hanging
Run
sbt test
.The test hangs forever.
Note that sometimes the test may fail with a pact server issue like
Cause: io.netty.channel.AbstractChannel$AnnotatedConnectException: finishConnect(..) failed: Connexion refused: localhost/[0:0:0:0:0:0:0:1]:33523
, ignore this case, and just retry. It's not the issue I care about for now.Expected behaviour
The test should succeed with output like:
It does when changing the
headers
value inMyWsClient
to any of these 3 other variants:Screenshots
N/A
Desktop (please complete the following information):
Additional context
The issue appears when upgrading from zio-http 0.0.5 to 3.0.0-RC4.
The text was updated successfully, but these errors were encountered: