Now at least OneTeam for OSX seems very confusing on which BOSH/http-bind URL it is going to connect and which certificate to verify (and doesn't give a choice to accept wrong certificate). Our http-bind is behind a reverse https proxy (port 443) on www.org.example (https://www.org.example/http-bind/) and JIDs are of form (user@jabber.org.example). Some BOSH/http-bind clients let me enter user@jabber.org.example with explicit http-bind URL of https://www.org.example/http-bind, OneTeam for OSX doesn't let me do it and instead has some magic on building the URL from JID and other preferences (like port, but not hostname). Furthermore certificate being returned should be compared against http-bind URL address (not domain from JID)? OneTeam just is SOOOOOO much nicer client than others and we really would need easier to use http-bind configuration to allow our society to work from transport like trains with strict port limitations and other "hostile" networks where https is the only option. :) Thanks.