Rub21 left a comment (openstreetmap/openstreetmap-website#7124)
yeah, a custom uploader that stores the file on S3 with `Content-Encoding:
gzip` makes more sense. I was trying to reuse the same upload path to keep the
PR simple, but now that you point it out, the custom uploader is the better way.
The download side gets simpler too. If the client accepts gzip, we redirect to
S3 and it will server the file, so the app stays out of the way. If a client
doesn't support gzip, the server unzips it and sends it plain. The server
already does that today when someone asks for /data.gpx, so it's not new
behavior,
For the old files, once the new compression is running, we could add a
background job that takes each plain GPX, gzips it, and re-uploads it with
`Content-Encoding: gzip`. but that is for other PR.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/7124#issuecomment-4731861023
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
