[HTTPS-Everywhere] HTTPS Everywhere plugin interfering with access to KDE.org websites

[Numismatika]

Fixing the developer issue seems to be easy, just removing the target
host and the rewrite rule.
Regarding the block dealing with files.kde.org, can we remove the test
urls and the following exclusion pattern now?


        <!--    Pages differ, various files 404:
                                    -->
        <exclusion
pattern="^http://files\.kde\.org/(?:$|.+/$|.+\.(?:btih|magnet|md5|meta4|metalink|mirrorlist|sha1|sha256|torrent)$)"
/>

Regards,
Numismatika

Am 06.01.2016 um 09:24 schrieb Ben Cooksley:
> Hello List,
>
> Resending this again. Configuring your mailing list to only accept
> mail from subscribers is extremely rude, especially when it is listed
> as the support / developer contact on Mozilla's addons.mozilla.org
> website.
>
> I'm now quite irritated. Please review the below and act expediently.
>
> Regards,
> Ben
>
> On Wed, Jan 6, 2016 at 9:16 PM, Ben Cooksley <bcooksley at kde.org> wrote:
>> Hi,
>>
>> I've received a report that your HTTPS Everywhere extension for
>> Mozilla Firefox is causing users of one of our websites problems.
>>
>> The issue concerns access to certain subpages of
>> http://developers.kde.org/. One of the remaining subpages is
>> http://developer.kde.org/~cfeck/portingstatus.html
>>
>> This is an older, and essentially retired subdomain that now primarily
>> redirects to techbase.kde.org (which fully supports https). It
>> therefore does not support https - it is only retained for legacy
>> compatibility.
>>
>> None the less, users are finding that their urls are being transformed
>> anyway - only instead of a non-working
>> https://developer.kde.org/~cfeck/portingstatus.html they get
>> https://techbase.kde.org/~cfeck/portingstatus.html - a URL which will
>> never work.
>>
>> This is not the first time such a report has been received in relation
>> to this specific subdomain - however in previous instances it was
>> thought to be cached browser behaviour or similar. A clear pattern has
>> now emerged that the HTTPS Everywhere plugin is at clear fault.
>> Disabling the plugin or otherwise rendering it inert resolves the
>> issue.
>>
>> I'd like to request you debug and correct the fault in your plugin as
>> soon as possible.
>>
>> Regards,
>> Ben Cooksley
>> KDE Sysadmin
> _______________________________________________
> HTTPS-Everywhere mailing list
> HTTPS-Everywhere at lists.eff.org
> https://lists.eff.org/mailman/listinfo/https-everywhere