Nixtla's Open Source Time Series Ecosystem.

Nixtla Community

Should I let the team know when I get an email to ops@ that's reporting a 500 internal server error?
Is that something that will always be on our side, or is that on the user side?

But come to read again, I think you’re talking about the requests we send to modal, not the ones we get from users?

So if the current limit is on the middleware I was hoping that sending a gzipped payload would bypass the limit, since the 80MB payload is 9MB compressed, but if the middleware will decompress it then it's no use

Ah wait, so you’re saying we could attatch a compressed gzip to the request

The client would compress the request, so we would have gzip inside gzip

This is what I tried:
```gzip current_payload.json # produces current_payload.json.gz of 9MB
curl -XPOST -H "content-type: application/json" -H "content-encoding: gzip" -H "Authorization: Bearer $NIXTLA_API_KEY" <https://dashboard.nixtla.io/api/cross_validation_multi_series> -d @current_payload.json.gz # send compressed req with content-encoding```
but it returns this error:
```<!DOCTYPE html>
&lt;html lang="en"&gt;
&lt;head&gt;
&lt;meta charset="utf-8"&gt;
&lt;title&gt;Error&lt;/title&gt;
&lt;/head&gt;
&lt;body&gt;
&lt;pre&gt;Bad Request&lt;/pre&gt;
&lt;/body&gt;
&lt;/html&gt;```
not sure where it's failing though

Hmmm, it’d have to be attached as multipart form data I think— ie a binary file 

And we might have to do something special in the middleware to handle it

I can experiment with it too once I get on my computer in a few hours 

Yeah that's what I was asking, usually you have to do some extra work when getting the request like checking the content encoding and manually decompressing the body (we don't do that in modal right now so it'd break there as well)

guys, chill, we have a 200mb limit which is giant for a json payload and it will improve in v2
I think you are over engineering a solution to a problem that we don't have.

Since modal doesn’t seem to be the bottleneck we could also get the binary in the middleware, decompress it, and send it as raw json to modal the way we do now— and not require modal changes 

I think it's a nice to have in terms of network bandwith as well, since the trade-off between sending 10x less data and decompressing it on the server could be worth it

Yeah, I think so too, worth experimenting. Will do when I’m back online

Alex confirmed things are working for him now. Thank you!