[JDEV] Bug: Status messages truncated before quote char

Fri Jul 13 11:45:25 CDT 2001

We're just using the current xdb_file...

--temas

  ----- Original Message ----- 
  From: Stanley Kurdziel 
  To: jdev at jabber.org 
  Cc: Thanh Nguyen ; Charles Owen ; Stanley Kurdziel 
  Sent: Thursday, July 12, 2001 7:41 PM
  Subject: RE: [JDEV] Bug: Status messages truncated before quote char

  Actually, I was composing an email regarding truncation of offline messages, when I saw your email :-)

  I am running jabber server 1.4.1 on Linux.

  This problem only happens when the receiving user is offline, and is not just restricted to status elements.   I noticed this problem during sending regular messages.   Here's the problem's I observed:
  1. Sending a message with <body>'message</body>   will end up with only <body>&apos;</body> in the <username>.xml file
  2. Sending a message with <body>"message</body>   will end up with only <body>&quot;</body> in the <username>.xml file
  3. Sending a message with <body>part1"part2</body>   will end up with only <body>part1</body> in the <username>.xml file
  4. Sending a message with <body>part1'part2</body>   will end up with only <body>part1</body> in the <username>.xml file

  Maybe it's a bug in xdb_file, since the messages are sent fine if both users are online.

  Interestingly, this does not happen on the jabber.org server...   Is jabber.org using xdb_file?   or xdb_<something else>
  Or has a fix been applied to jabber.org?

  Thanks for any information,

  -sek

  -----Original Message-----
  From: Jens Alfke [mailto:jens at mac.com]
  Sent: Thursday, July 12, 2001 12:03 PM
  To: jdev at jabber.org
  Subject: [JDEV] Bug: Status messages truncated before quote char

    I have noticed that status messages (i.e. <status> elements in a <presence> element) containing a quote character are truncated before that character — but only when forwarded by the server upon client login, not when they're sent in real time to an already logged in client. 

    I've verified that my client sends XML metachars properly to the server, and that the problem exists in the raw XML received by the client, not in my XML parsing. 

    This is with the 1.4.1 server running on Solaris. Anyone else seen this? 

    —Jens

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20010713/9281001c/attachment-0002.htm>