This seems to be resolved for 1.39 for zero config VE installs thanks to T305108, I tried it out and did not come across any issues for the three URL types you list.

Indeed, I tried it out, it works fine! That's great news. Would this task still be relevant for setups where Parsoid is hosted separately (I have no clue about how such setups are used in practice), or can it be closed?

We just tested it on MediaWiki 1.36.2 and can confirm the bug is still present.

You are right, there are no custom mime maps registered (as far as we know). We also agree that MediaWiki does provide a consistent cross-platform experience by using a built-in mime map. However, it is quite unfortunate that this code might contain bugs such as the one linked. We personally feel the benefits of using a specialized library, such as PHP finfo, could outweigh its disadvantages. Still, it is up to the MediaWiki team to balance these arguments and decide which is best.

Thanks, we were unaware of this hook. The documentation on https://www.mediawiki.org/wiki/Manual:Hooks/APIGetAllowedParams is also very unclear about the purpose of this hook. According to https://www.mediawiki.org/wiki/Category:APIGetAllowedParams_extensions it's not too widely used, so many developers might not be aware of it either. As a result, it might still be more intuitive for unrecognizedparams to be removed. Do you know why the unrecognizedparams warning was added?

Looks right, thank you!

Can you confirm that https://gerrit.wikimedia.org/r/c/mediawiki/extensions/LDAPAuthorization/+/702976/ didn't address you use case properly?

Hi, it's been a while since we last talked about this, so I wondered what your thoughts are on the approach of using an LDAP search filter string. Our organisation can look into helping with its implementation, if it sounds good to you.

That's great, thanks a lot!

Thanks for your reply! We appreciate the help. Also thanks for sharing the migration documentation link. For our skin, however, we planned to fully rewrite it from scratch because it currently uses a lot of old functionality and is kind of a mess. Therefore we hoped someone with little PHP experience would be able to build the skin, because it's Mustache so it would only require HTML and CSS knowledge.

Sure, the following pages outline how to configure that extension:

Quoting https://ldap.com/ldap-filters/ :

In T280875#7197180, @Osnard wrote:

I have implemented a change: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/LDAPAuthorization/+/702976/3..4/tests/phpunit/Requirement/MatchAttributesTest.php
But now other tests hat to be changed. @MarkAHershberger What do you think. Does it match your expectation this way?

Could this be related to T226693?