`Content-Length` header through edge proxy

Content-Length

header through edge proxy

kevqiu

PROOP

2 months ago

Project: 7478ce1e-4747-4053-b4f8-97bcc9661c03

I have a client (ESP-32 OTA) that requires the Content-Length to be present in the response headers. It looks like the railway edge proxy strips out that header and applies the Content-Encoding header. The response I'm looking to return is an octet-stream of a binary file.

So far I've attempting serving this file from the MinIO SDK via an NextJS endpoint and generating pre-signed URLs from MinIO.

Is there any way to bypass the header stripping so that I can retain the Content-Length header?

Solved

2 Replies

brody

EMPLOYEE

2 months ago

Thanks for the detailed report. This is a known behavior where our edge proxy strips the Content-Length header from responses, and we're tracking it. Glad to hear private networking is working as a bypass for your use case.

brody

EMPLOYEE

2 months ago

This has been fixed.

Status changed to Solved medim • about 2 months ago

Welcome!