Fun and Games with HTTP

Previously...

• I made the changes in mod_megaphone to send back an HTTP response.
• I fixed an issue with an array growing without bounds
• I fixed an issue with HTTP headers

So now that the connections are more or less working and megaphone is not putting in a bunch of extra HTTP headers things still don't work.  There was an issue with keep alive and nodejs, but I think I have that one working.  At this point, the authentication portion of the handshake is failing and I'm not sure why that is happening.

As I see it, here are my options:

• Try and figure out why the current approach is not working.
• Modify ejabberd_http to use the megaphone protocol.

I'm not too keen on either approach to be honest.  I don't understand why the current approach is not working --- the connection should look pretty much the same that it does to pidgin as when it is talking directly to ejabberd.  This being the case, I'm not sure where to start with why the authentication is failing.

Modifying ejabberd_http really does not excite me either since that means mucking about with a log of code that I don't understand.  In addition, it means changing the ECM side so that it accepts straight TCP connections instead of HTTP.  The good side of working on this approach is that at least I will have something to compare with - there should be no difference between how the ejabberd connection and the ECM connection appear.

Yet more decisions.