ssl through proxy broke between 4.6 and 4.7

[Andrew Kohlsmith]

I use ssh -D to create a SOCKS5 proxy and drive all of my network traffic through it. I use a .pac file to configure this and set KDE to use it through the system settings.

e.g. ssh -D 8080 <email address hidden> establishes the proxy, and the proxy.pac file configures the exceptions (local network, etc.).

I also have a DAViCal server on that same server. I access it through https://<email address hidden>/blahblah and with the standard Kubuntu packages it worked fine.

cal.my.domain has the same IP as the ssh server I am connecting to to establish the SOCKS5 proxy.

Upon upgrading to 4.7 through the kubuntu backports PPA this broke. For some reason KDE cannot establish an SSL connection to the server through the socks5 proxy. I had to add a specific exception such that the proxy is not used to connect to my davical server (which is also the socks5 proxy).

I'm not sure if KDE 4.6 did it right, or if 4.7 is doing it right and the exception is really what should be done, but I'm posting this bug report so that it can be evaluated.

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!