Hi, Currently ALPN is only a SHOULD for the client implicating that the XEP will work also without ALPN.
For that reason the XEP states that a server admin should also provide other records not using ALPN to which the client can fallback. What is not clear from the XEP, and did come as a suprise, is how the connection fails when connecting without ALPN. I think most clients have a fallback implemented on failed TCP connection, and i think devs who read the XEP think: Ok no problem i got this. What is actually needed so this XEP is implemented without ALPN, is a automatic fallback on invalid XML to other SRV Records. This not really made clear by the XEP and i think its not something Clients do naturally. Now im no expert on this, but is this even something we want Clients doing (Fallback on Invalid XML) In my opinion ALPN should be made a MUST for Clients. Regards Philipp 2018-01-09 18:10 GMT+01:00 Jonas Wielicki <[email protected]>: > On Dienstag, 9. Januar 2018 11:55:15 CET Florian Schmaus wrote: > > - Invalid XML (how could that happen BTW?) > > When you end up at an HTTP service instead (will probably be the default on > services which run on 443). You send XML (stream header), you get 400 Bad > Request back. > > kind regards, > Jonas > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ > >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
