Andreas Ernst wrote:
Error in lobbyUpdateHandler() - 411 after entering a room listUsersInRoomHandler() - 411
Well, I did a lot of screaming and yelling, but I *finally* figured out what was going on...
I was fianlly able to replicate the issue, but it only came up with a certain combination... using Firefox when accessing the live demo running in Resin. This is a good bit of info for anyone doing AJAX, so here's what was happening...
The 411 response code, which *is* an HTTP response code by the way, indicates that the server rejected the request because no Content-Length header was set. At first this didn't seem odd because when I checked headers, from IE anyway, Content-Length was set to 0, so no error. But wait... ZERO?? Then it dawned on me: I was POSTing all the AJAX requests, but none of them were actually sending body content, hence 0 was correct. Well, it seems that FF doesn't set that header in that case.
Well, Tomcat DOES NOT seem to send a 411 response in this case anyway. So, when I did my testing on Tomcat, with both IE and FF, no error ever happened. Now, with the app deployed on Resin, the error STILL does not happen with IE because IE doesn't throw an error when it gets a 411 back (or it's sending the header where FF is not, I'm not 100% sure which it is). The bottom line though is that it's ONLY with the combination of Firefox and Resin that this occurred, which is why I never saw it myself before release.
Anyway, the fix is simple and obvious: all the AJAX requests are now GETs. The live demo now seems to work for FF and IE equally.
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
