Newlines in the stream tag are not handled properly
Sjoerd Simons reports that Openfire appears to be having problems parsing newlines. In a Windows environment, the client does not get any reaction from the server if the newlines in the stream tag consist of a \n character only. If the newline consists of \r\n, all is well.
Thanks @csh , lets close this for now until somebody reproduces it. We can always reopen...
The description is not very clear, but I've tested the following (Openfire 3.8.2 on Windows 7, client too):
with a \n at the end does not harm (neither does \r\n)
did also not harm.
Anybody still watching this issue able to comment on its current applicability to 3.9.1 release?
Removing the 'fix version' for all unresolved issues that were scheduled for version 7.8.2. We're releasing this version today - the remaining issues should be rescheduled later.
Question... why would you put a \n in a stream tag? Is it a particular client that does this?