Format 0 must be utf-8

[awwright]

Format 0 is defined as text/plain; charset=utf-8. By definition, text/* defaults to US-ASCII and causes encoding problems if a Unicode-encoded document is served without this charset parameter - e.g. in CoAP-to-HTTP translators.

Instead, the module serves option 0 as merely text/plain i.e. US-ASCII.

[mcollina]

Good catch! Would you like to send a PR?

[awwright]

How would these cases be handled:

res.setOption('Content-Format', 'text/plain');
// vs.
res.setOption('Content-Format', 'text/plain;charset=utf-8');
// vs.
res.setOption('Content-Format', 'text/plain; charset=utf-8'); // whitespace

Is anyone currently using the first when they intend the second/third options?

Should equivalent forms be handled? (I maintain a library to parse these Media type formats, "contenttype")

[mcollina]

Anyway, it's a bug. The spec it's clear that's utf-8, and it is how is parsed by node-coap anyway.
Basically, it's just the wrong string.

Pick what version suits you most of the other two.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.

[stale]

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions.

[JKRhb]

Reopening this issue as the bug is still present.