Replies: 1 comment
-
Seems like an invalid header, but we should at least handle it more gracefully. Please create an issue. PRs welcome |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello :)
I am not sure whether I should put this in discussions or issues, so I will just write it here and if needed I can move it later.
Using the declarative Micronaut Http Client I have come across a NullPointerException which is caused by the Netty ClientCookieDecoder not being able to decode the set-cookie header from the response and returning a null which is not properly handled by the NettyCookies(HttpHeaders nettyHeaders, ConversionService conversionService) constructor.
The client is pretty straightforward
And I have no additional configuration in the application.yml file
I have tried to debug the issue by enabling trace logging and I can see that the server is returning a response as needed but Micronaut terminates the stream and I get the following error
The header in the response which causes the error is
23:42:32.026 [default-nioEventLoopGroup-1-2] TRACE i.m.h.client.netty.DefaultHttpClient - Set-Cookie: HttpOnly;Secure
Btw If it is of any importance I am trying to access a server with a self signed certificate. I expect that I would also need to either whitelist the certificate or include a configuration to ease the rules of the http client.
Regards.
Beta Was this translation helpful? Give feedback.
All reactions