- 'ver' -- This attribute specifies the highest version of the BOSH protocol that the connection manager supports, or the version specified by the client in its request, whichever is lower.
- 'to' -- This attribute communicates the identity of the backend server to which the client is attempting to connect.
Strangely enough, neither server includes the "to" attribute in their response, despite the fact that the spec explicitly calls for it.
At any rate, adding the ver attribute did not seem to make a difference.
I switched over to wireshark and noticed that NXB was using chunked encoding whereas ejabberd was not. The docs say that to turn off chunked encoding, you need to set a content-length so I did that and immediately noticed that the conversation between NXB and Pidgin lasted longer.
This brought me to the current brick wall: Pidgin complains about getting an "Invalid response from server." What is invalid about the response? Beats me. Looking around I did not find any way of displaying a more detailed error message for Pidgin short of creating a plugin or perhaps starting it from the command line.
Next step is to take a look at the differences between the conversations between ejabberd and NXB and see if I can spot any differences.
And I still don't know if putting the features stanza in the first response made any difference.
Fooies.
Postscript: I tried out running pidgin from the command line and displaying the debug log. Go me!
No comments:
Post a Comment