-
Notifications
You must be signed in to change notification settings - Fork 355
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
NettyConnectorProvider (jersey-netty-connector) doesn't send query parameters in the Get Request #4369
Milestone
Comments
Did you try:
or
instead of
as DefaultFullHttpRequest constructor parameter? |
Fixed by #4393 |
This was referenced Jun 26, 2021
This was referenced Aug 5, 2021
This was referenced Aug 30, 2021
1 task
This was referenced Oct 4, 2021
This was referenced Oct 18, 2021
This was referenced Oct 21, 2021
Merged
Merged
This was referenced Oct 21, 2021
Closed
Closed
1 task
1 task
This was referenced Mar 7, 2022
This was referenced Mar 15, 2022
This was referenced Apr 17, 2022
This was referenced May 3, 2022
1 task
This was referenced Oct 19, 2022
1 task
1 task
1 task
1 task
This was referenced Apr 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to send an HTTP request with query parameters using Jersey Client and setting NettyConnectorProvider (org.glassfish.jersey.connectors:jersey-netty-connector:2.25.1) as a provider to the config (org.glassfish.jersey.client.ClientConfig) by the method connectorProvider().
I tried to send the query parameters using the method queryparam(), but the values are not sent on the request.
Looking in the source code of NettyConectorProvider, it uses the method requestUri.getRawPath()) during the creation of DefaultFullHttpRequest, but this method returns the path without the query parameters.
nettyRequest = new DefaultFullHttpRequest(HttpVersion.HTTP_1_1,
HttpMethod.valueOf(jerseyRequest.getMethod()),
requestUri.getRawPath());
How can I send query parameters in a GET request using NettyConnectorProvider or is there a knowledge issue related to query parameters?
The text was updated successfully, but these errors were encountered: