Hi, The patch works fine! Is it also possible with GET to move the call of the program up? Setting self.rerequest_attempts = 1 doesn't change the behaviour like it did with POST because there are some checks against has_data which naturally fail because a GET doesn't have data. The Z_PORT_GROUP has the same effect here like Z_PORT_EXACT with the 3s waiting time. But I don't mind about just using the Z_PORT_ANY as it's not really a big difference. I think I just stumbled over a problem in the prerelease 3.3.1. I just used a plain policy file for HTTPS in 3.3.1 as well as in 3.1.4. It looks like this: class HttpsProxy(PsslProxy): def config(self): PsslProxy.config(self) self.client_need_ssl = TRUE self.client_key_file = '/home/zorp/conf/server.key' self.client_cert_file = '/home/zorp/conf/server.crt' self.client_verify_type = PSSL_VERIFY_NONE self.server_need_ssl = TRUE self.server_ca_directory = '/etc/zorp/https_trusted_ca.crt' self.server_verify_type = PSSL_VERIFY_NONE self.stack_proxy = HttpProxy However, this does not work in 3.3.1 anymore. I've uploaded the logfiles at http://pastebin.com/f11e4da70 (3.1.4) http://pastebin.com/f2a09d626 (3.3.1; really ends at this point and the browser waits for data!) It looks like in 3.3.1 the HttpProxy is stacked when the Pssl proxy is already in the process of shutting down and thus it doesn't transfer correctly. Is there a different syntax in the policy file needed? Thomas Wenz -- Psssst! Schon das coole Video vom GMX MultiMessenger gesehen? Der Eine für Alle: http://www.gmx.net/de/go/messenger03