@mmn@social.umeahackerspace.se As we discussed already regarding "SSL Mode" in AndStatus, indeed, it would be good for a client application to adapt to a server automatically.
But as for an "SSL Mode", for the second option: "Use legacy HTTP protocol" - automatic discovery _during normal operation_ of a proper connection option is not practical. Because this will mean substantial time delays and network traffic increase. E.g. in this "411-content-length-required" case, for each attempt to send a message with an attachment, AndStatus will first do failed attempt and succeed on a second attempt only.

I think we better integrate such server parameters discovery into Account creation / verification. Which may be repeated on User's explicit request to "Reverify account".
?!

@moshpirit quitter.se @andstatus@quitter.no @lnxw48@fresh.federati.net @knuthollund@quitter.no @mcscx@quitter.se