XML-RPC problem when checking content_type header about dokuwiki

[Cherrg]

Hi there,
some background information why the suggestion of @splitbrain is a valid solution and why this is actually a bug:

The bug was introduced on Jun 9, 2023 with this commit: cc7691a
and breaks existing xml-rpc client implementations.

The Content-Type header should be part of the internet protocol standard. E.g.:

• RFC 2616 -> (drafted 1999, obsolete)
• RFC 7231 -> (proposed standard June 2014, obsolete)
• RFC 9110 -> (current standard, since 2022)

Quote from RFC 5987 (obsolete) / RFC 8187 - this is about the charset

Note: recipients should be prepared to handle encoding errors,
      such as malformed or incomplete percent escape sequences, or non-
      decodable octet sequences, in a robust manner.  This specification
      does not mandate any specific behavior, for instance, the
      following strategies are all acceptable:

      *  ignoring the parameter,

      *  stripping a non-decodable octet sequence,

      *  substituting a non-decodable octet sequence by a replacement
         character, such as the Unicode character U+FFFD (Replacement
         Character).

I remember seeing an RFC specification that contains several formats with and without spaces for the character set in the content type header. -> rfc7231#section-3.1.1.1
Also check https://www.w3.org/Protocols/rfc1341/4_Content-Type.html for the complete definition of the content-type header field.

The charset is an optional part of the Content-Type header. Please just ignore the charset, or check for utf-8 if dokuwiki assumes this charset. It is even possible to specify the requested charset in an answer: Accept-Charset.

Funnily enough, the responses that the xmlrpc-api produces contains the following content-type header: “text/xml; charset=utf-8", however, currently does not accept this content type as before.

Have a nice day.

[mprins]

I don't think it is a bug if software follows the specification: http://xmlrpc.com/spec.md

required headers are:

• A User-Agent and Host must be specified.
• The Content-Type is text/xml.
• The Content-Length must be specified and must be correct.

Reading https://datatracker.ietf.org/doc/html/rfc7231#section-3.1.1.1 learned me that the value of content type must be interpreted case insensitively