<-- back to the mailing list

Adding a content size meta?

Jason McBrayer jmcbray at carcosa.net

Tue Jan 21 15:30:43 GMT 2020

- - - - - - - - - - - - - - - - - - - ```

solderpunk <solderpunk at SDF.ORG> writes:

> 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).

Personally, I feel like request-and-terminate is the better approach;it's easier on server developers to correctly handle dropped connections(which you have to do anyway), as opposed to implementing a separateroute for dynamically-generated metadata responses. I'm strongly againstreturning JSON metadata, because it opens the door to unlimitedextensibility.

-- Jason McBrayer      | “Strange is the night where black stars rise,jmcbray at carcosa.net | and strange moons circle through the skies,                    | but stranger still is lost Carcosa.”                    | ― Robert W. Chambers,The King in Yellow