pablobm left a comment (openstreetmap/openstreetmap-website#7124)
> What I'm questioning is whether we need to automatically decompress them give
> we already have compressed traces and don't do that for them.
Right. As I see it, currently this is what happens:
1. User uploads a GPX: we store the GPX exactly as given. If later downloaded,
the user gets this GPX file.
2. User uploads a gzipped GPX: we store the gzip. If later downloaded, the user
gets the gzip, it's their problem to decompress it. After all, they surely were
able to compress it in the first place.
3. Same for all other types of file.
This PR changes the first case:
- User uploads a GPX: we compress it and store it as gzip. If later downloaded,
the user will get a GPX and won't need to decompress it themselves (which
particularly for Windows users would be problematic). All this while delegating
the decompression to the browser by specifying the `Content-Encoding`.
End result: on download, users get exactly what they uploaded, avoiding
confusion. We do something clever in the middle to compress/decompress with
minimum impact to our infrastructure.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/7124#issuecomment-4767085065
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/7124/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
