Compressed POST payloads in RestExpress?

[Paul Vaillancourt]

I am trying to send gzipped payloads to my RestExpress server POST routes to reduce the amount of data going over the wire. I see that RestExpress by default will gzip the response, but what about a request? Do i need to implement the decompression with a preprocessor?

[Todd Fredrich]

Hi Paul,

The Netty pipeline that gets setup by RestExpress does handle incoming gzipped requests as well as gzip responses. The pipeline is configured with a https://netty.io/4.0/api/io/netty/handler/codec/http/HttpContentDecompressor.html and should handle it correctly. It does, however, depend on the request headers to decode correctly.

Thanks,

--Todd

[Paul Vaillancourt]

Thanks for the response Todd. I got the gzipped payloads to work with curl, up to a point. We have the restExpress.max.payload.size set to 700k on the server, but any POST requests with binary data over  ~2.5k seem to have the request blocked, and is not even getting to the controller method.

The restExpress.max.payload.size applies to binary data, too, correct?

Thanks,

Paul

[Ori S]

Sounds like a proxy is sitting in front of RestExpress, could that be the case? If so, check that the proxy is also configured to allow the same data packet size.

/OS

[Paul Vaillancourt]

Ori,

Thanks, but i see this on my local machine, too. No proxy...

[Todd Fredrich]

Hi Paul,

It seems like there's something else going on as when the max payload size is exceeded, an error is returned--the request doesn't block. If this endpoint is being called repeatedly, perhaps the number of connections on the machine (ephemeral ports) are exhausted? Maybe try upping the ulimit. If the HTTP client is using 1.0 instead of 1.1 the connection keep-alive could be getting messed up. Or other weirdness like that. Sorry I can't help more without deeper information.

--Todd