Prefer exact match without parameters to match with extra parameters.

[suola]

If server supports both 'type/subtype' and 'type/subtype;param=foo', a request which accepts 'type/subtype' should be served with 'type/subtype'. Currently the extra parameter is not taken into account when determining the preference of the two types, and preference is selected by order of the types.

Relevant PR in mimeparse:

falconry/python-mimeparse#36

[vytas7]

Indeed, that sounds like a logical suggestion.

FWIW, we vendored python-mimeparse into Falcon as part of the 2.0 release as it was the last dependency.
In that light, a question arises what to do with your PR if we agree to go ahead with it. Maybe we should ask @dbtsai to take over maintenance of the project 🤔 Or whether we should fork our version.

[vytas7]

Note that I'm reluctant to label this as a breaking change, as we don't seem to provide exact guarantees how subtypes are chosen.

[vytas7]

Related:

• Vendoring python-mimeparse (implemented as of Falcon 2.0) Consider vendoring python-mimeparse #1420
• Discussion re contributing back to python-mimeparse / its maintenance Contribute optimizations to the python-mimeparse project #1183

[vytas7]

@suola I know this has taken us a long time, but the issue has finally been fixed in 4.0.0.
See the description of the new algorithm here: falcon.mediatypes.quality().