On 2017-06-14 22:42, Mark Shane Hayden wrote: > I am having a peculiar problem with the windows desktop client since > upgrading our dev system to 4.4. > > I can connect fine with my Debian machine however my colleague cannot > connect on his Windows machine. Upon further investigation it appears that > his machine immediately sends HTTP to the server upon connecting and the > server is configured to reject unencrypted connections to port 8000 > (returns HTTP 400 unless it is encrypted). I even tried making the server > send a 307 redirect to https but the Windows client ignores it. > > Is this a new bug? Something we overlooked on client setup for Windows? Is > there still no way to force the client to never attempt insecure > connections?
You have to clean the known_hosts configuration: http://doc.tryton.org/4.4/tryton/doc/usage.html#configuration-file This is were the client keep track of which servers use SSL or not. -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/ -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/20170615080801.GP3591%40kei.
