| Table of Contents |
|---|
Any non-ASCII characters in your metadata are encoded for storage. To Swarm encodes header field content according to the rules of RFC-2047 to comply with HTTP/1.1 per RFC-2616, Swarm encodes header field content according to the rules of RFC-2047, which means that characters . Characters in sets other than ISO-8859-1 must be encoded.
What this means is that you might see encoding Encoding of non-ASCII characters may appear in the metadata details for an object that you view viewed in the Content UI:
...
Swarm allows all string-typed header fields to have multiple lines as well as encoded words. Swarm stores the header value as-is with the object metadata. Only It decode the value when Swarm needs to use that value (such as for metadata indexing) does it decode the value. Swarm decodes header fields into Unicode and then operates on the decoded values. The original encoded persistent headers , however, remain safely stored with the object and are returned when you retrieve the object is retrieved.
For Swarm's handling of metadata, see See Encoding Non-ASCII Characters in Metadata for Swarm's handling of metadata.
| Child pages (Children Display) |
|---|