Projects tigase _server server-core Issues #221
“amp” rule should not be delivered to the message recipient (#221)
Aman Mishra opened 1 decade ago

When a client sends a message containing an “amp” rule to another client, the “amp” rule is processed at the server, but an “amp” tag containing an empty “rule” tag is delivered in the message to the recipient.

For example, if the client sends the following message:

Hello

The following message should be received at the recipient:

Hello

However, the following message is received:

Hello

The “amp” rule should be processed at the server and should not be delivered to the message recipient. Can you look into this and let us know when you can provide a fix for this?

Artur Hefczyc commented 1 decade ago

Did not notice that before. We will fix it, as this is a bug in the core Tigase code I am moving this bug to the Tigase server project. Will be fixed for the version 5.2.0 release.

Artur Hefczyc commented 1 decade ago

Please fix it before Beta3 release if possible #1499.

Andrzej Wójcik (Tigase) commented 1 decade ago

I tried to reproduce this issue but when I send message with amp rules they are processed and all rules are included in message delivered to recipient so packet delivered to recipient would look the same as packet sent by sender.

Do you have any hints on how to reproduce this issue?

I also could not find in XEP-0079 any informations that would suggest that amp tag should be removed after being processed and before sending message to the connected client.

Aman Mishra commented 1 decade ago

Thanks for the clarification Andrej,

It's true that XEP-0079 does not suggest that amp tag should be removed after being processed. However, in that case clients will need to handle the amp rules.

This ticket can be closed for now, but do let us know if this can be implemented in the future using a component level configuration.

Regards,

Aman

issue 1 of 1
Type
Bug
Priority
Major
Assignee
RedmineID
1485
Version
tigase-server-5.2.0
Spent time
12h
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/server-core#221
Please wait...
Page is in error, reload to recover