Get Hot New Stuff - Legacy Endpoints and Multiple Requests (Discover?)

Ben Cooksley bcooksley at
Fri Jan 31 07:34:58 GMT 2020

On Fri, Jan 31, 2020 at 1:05 AM Michael Reeves <reeves.87 at> wrote:
> There seems to be some sort of ssl certificate issue with On kubuntu this triggers a warning as soon as discover starts that may be a contributing factor.

I've checked and can find no fault with Both wget
and kioclient5 raise no objections on my system, and both Chrome and
Firefox are perfectly happy with it as well.

The Qualys SSL Server Test also confirms that we have no setup issues
(aside from including the root certificate in the chain we send, which
is harmless).
The results of that test can be found at

I'm afraid the fault is either with Kubuntu (which I highly doubt) or
your local network (much more probable) in this instance.

Should you believe the fault is on our side I will need information
from the "Details" pane as to why KIO refuses to trust connections to on your system.


> On Thu, Jan 30, 2020, 4:20 AM Ben Cooksley <bcooksley at> wrote:
>> Hi all,
>> While diagnosing an issue this evening with, I noticed
>> that we are still getting an extremely large number of requests for
>> the legacy OCS/GHNS providers.xml endpoint, which is supposed to only
>> exist for compatibility with older applications.
>> Looking on LXR i've found that a substantial number of our
>> applications are still using the old url in their most recent releases
>> (see
>> All new code should be using now, and all old code
>> should be transitioning to using the new url.
>> The legacy url is significantly more resource intensive for our
>> servers to support and our ability to scale this endpoint is
>> substantially more limited when compared with the new endpoint so it
>> is important that this is moved over (to the extent Enterprise/Long
>> term LTS distributions should be encouraged to patch this)
>> Additionally, I believe there to be a multiple request bug somewhere
>> as this endpoint is being hit approximately 3-4 times in the same
>> second for each client we see. Based on the corresponding hit to
>> which happens at the
>> same time it is likely the application showing this fault the most is
>> Discover.
>> If we could please get the above all fixed up that would be appreciated.
>> Thanks,
>> Ben

More information about the kde-core-devel mailing list