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
If the resource is retrieved directly from the file system, set supplied-type to the MIME type provided by the file system.
This is not clear. File systems store up to three pieces of data about each file:
The name of the file.
The contents of the file.
Metadata about the file.
As a result there's a few ways to interpret that instruction:
Use the filename to determine the supplied MIME type. -- If this is what was intended, then the spec should have rules for determining a MIME type from a filename.
Use the file's contents to determine its supplied MIME type. -- I don't think that this was what was intended because other parts of the spec talk about determining MIME types based on contents.
As part of the file's metadata, the file system stores its MIME type. Use that MIME type as the supplied MIME type. -- This seems like what was intended, but I haven't been able to find any evidence that there's file systems that store a files MIME type.
Some combination of the previous interpretations.
It also might be more accurate to say:
If the resource is retrieved directly from the file system, set supplied-type to the MIME type determined by the operating system.
The text was updated successfully, but these errors were encountered:
According to the supplied MIME type detection algorithm,
This is not clear. File systems store up to three pieces of data about each file:
As a result there's a few ways to interpret that instruction:
It also might be more accurate to say:
The text was updated successfully, but these errors were encountered: