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? Thanks in advance... -- 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/5f2320c8-892a-40f7-b7fb-0af7a08db711%40googlegroups.com.
