HTTP (conditional) range requests

[jakubbartel]

Hi, what is generally the approach to handle range requests? Is echo going to support Range Etag etc. headers in the future or it's not supported on purpose?

At the moment I'm using other http router and wrapping each response with http.ServeContent. I would love to migrate to echo but partial response support is a mandatory requirement - to serve in-memory blob data.

I've found this answer but the approach (if it still works) doesn't seem very scalable and idiomatic.

Is it a good idea to implement a range requests middleware?

Thanks!

[aldas]

Echo uses internally standard library http.ServeContent to serve files and/or anything that implements io.ReadSeeker interface.

https://pkg.go.dev/net/http#ServeContent

ServeContent replies to the request using the content in the provided ReadSeeker. The main benefit of ServeContent over io.Copy is that it handles Range requests properly, sets the MIME type, and handles If-Match, If-Unmodified-Since, If-None-Match, If-Modified-Since, and If-Range requests.

This is where it happens

echo/context_fs_go1.16.go

Line 50 in 5ebed44

http.ServeContent(c.Response(), c.Request(), fi.Name(), fi.ModTime(), ff)

You your inmemory data can not be used as files then just create helper function to output from memory by passing your data to http.ServeContent