You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to return the actual coding system for a file, we'd need to know how the file was encoded when it was written to the hyperdrive.
IIUC, the standard way to specify a file's encoding in a PUT request is in the Content-Type header, e.g., Content-Type: text/plain; charset=ISO-8859-1.
Once hypercore-fetch receives the file and its coding system, where should the encoding metadata be stored?
We could put it alongside the mtime metadata in entry.value.metadata.encoding. WDYT?
The text was updated successfully, but these errors were encountered:
Currently,
hypercore-fetch
assumes that all text files are UTF-8 when returning aContent-Type
header:In order to return the actual coding system for a file, we'd need to know how the file was encoded when it was written to the hyperdrive.
IIUC, the standard way to specify a file's encoding in a
PUT
request is in theContent-Type
header, e.g.,Content-Type: text/plain; charset=ISO-8859-1
.Once
hypercore-fetch
receives the file and its coding system, where should the encoding metadata be stored?We could put it alongside the
mtime
metadata inentry.value.metadata.encoding
. WDYT?The text was updated successfully, but these errors were encountered: