You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a bit hard for me to produce a minimal failing test case but I can show you exactly where the problem is.
I am forwarding some large files from openstack swift via jetty, jax-rs-client and the jdk-connector (because the performance seems way way better for big files)
In org.glassfish.jersey.jdk.connector.internal.HttpParser there's a method called decideTransferEncoding where it expects the content length to parse as an int. This fails when the response size is greater than Integer.MAX_VALUE. There might be more issues with this further on down the line, but this was the first one I hit. If I get some time I'll try and get you a patch, but for now I'm going to try and work around it.
The text was updated successfully, but these errors were encountered:
Note that for large files, chunked encoding is far better than a buffered stream. Use client.property(ClientProperties.REQUEST_ENTITY_PROCESSING, RequestEntityProcessing.CHUNKED).
It's a bit hard for me to produce a minimal failing test case but I can show you exactly where the problem is.
I am forwarding some large files from openstack swift via jetty, jax-rs-client and the jdk-connector (because the performance seems way way better for big files)
In
org.glassfish.jersey.jdk.connector.internal.HttpParser
there's a method calleddecideTransferEncoding
where it expects the content length to parse as an int. This fails when the response size is greater thanInteger.MAX_VALUE
. There might be more issues with this further on down the line, but this was the first one I hit. If I get some time I'll try and get you a patch, but for now I'm going to try and work around it.The text was updated successfully, but these errors were encountered: