On Sat, Jan 18, 2020 at 06:58:26PM +0100, Brian Evans wrote: > julienxx writes: > > Could we imagine a standardized way to query > an URL just for it's meta header maybe? > > I have just been requesting the document reading > the first line and then severing the connection. > > > I do agree that having content size, pref in bytes, in > the meta would allow for loading animations, > percent counters, download managers, etc. Which > would benefit the user of any client. I guess the question is whether we prefer adding this information into the response header and having clients do the request-and-terminate trick, or defining a well-known endpoint servers can implement which takes a path as an input and returns either what the response header would be, or maybe a small JSON structure of metadata (which could include stuff like last-modified date). Cheers, Solderpunk
---
Previous in thread (4 of 7): 🗣️ Brian Evans (b__m__e (a) mailfence.com)
Next in thread (6 of 7): 🗣️ Jason McBrayer (jmcbray (a) carcosa.net)