<snip>
> So you're getting TWO 404 errors when trying to federate with a non-
> existing wave server?

Yes.  First, it tries to discover using the domain name.
noexistentwavedomain.com
I get a 404 error, so it then tries to discover specifically on the wave
component
wave.noexistentwavedomain.com

Since neither server exists, I get two 404 errors.

<snip>

> Now I'm even more confused. :-) What do you think: Does this error
> always mean that the destination server could not be found? Or does it
> mean that my own server could not be found BY the destination server?

As I currently understand things, you send a request and do not get a reply.
Possible reasons for not getting a reply could include:
Bad DNS name
Remote Server not currently running
Remote Server unable to deliver its reply back to you.

Given that I'm managing to get a reply back from initech-corp.com, it would
seem that options one and two are not likely the case and the more likely
cause would be that the remote server cannot deliver it's reply back to you.

To test this, I try
telnet initech-corp.com 5223 to make sure I can connect to the XMPP server.
If I can't get a connection, that points to one or two. If I do get a
connection, that points to three.

<snip>
> When saying "adding signed certificates to my Openfire server", do you
> mean you've added certificates to Openfire via its Web UI?

Yes, I'm talking about added signed certificates to the Openfire server via
the Web UI.  I don't know if some XMPP servers are requiring encrypted
communications using a signed certificate.  However, it doesn't hurt to do
this step.  In fact, it is probably a good idea no matter what.

Aldon


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Wave 
Protocol" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/wave-protocol?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to