a month ago
Our app has no compression middleware, but its direct Railway endpoint returns gzip responses.
Is HTTP egress billed before or after Railway’s proxy compression? Would adding gzip in the app reduce billed egress?
1 Reply
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Egress is billed before our edge compression. We measure it as bytes leave your service's container, before the response reaches our proxy, so the gzip you see from the edge doesn't lower your billed egress.
Compressing responses in your app does reduce it, because the smaller compressed body is what leaves the container and gets counted. The edge won't compress a response again if it already arrives encoded.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago