Newlines in the stream tag are not handled properly

Description

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.

Environment

None

Activity

Show:
Daryl Herzmann
February 14, 2014, 3:10 PM

Thanks @csh , lets close this for now until somebody reproduces it. We can always reopen...

csh
February 14, 2014, 3:01 PM
Edited

The description is not very clear, but I've tested the following (Openfire 3.8.2 on Windows 7, client too):

Sending

with a \n at the end does not harm (neither does \r\n)

The following:

did also not harm.

Daryl Herzmann
February 14, 2014, 2:31 PM

Anybody still watching this issue able to comment on its current applicability to 3.9.1 release?

Guus der Kinderen
February 6, 2013, 7:57 PM

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.

Wayne Franklin
November 2, 2010, 5:19 PM

Question... why would you put a \n in a stream tag? Is it a particular client that does this?

Incomplete

Assignee

Guus der Kinderen

Reporter

Guus der Kinderen