API: Rejected incoming message - Githubissues

jaros1 / Money-Network

Demo with complementary and alternative money. Implemented in ZeroNet and AngularJS. Focus on privacy, encryption, max data in client and min data on ZeroNet. Work in progress.

GNU General Public License v2.0

4 stars 4 forks source link

API: Rejected incoming message #300

Closed jaros1 closed 6 years ago

jaros1 commented 6 years ago

MoneyNetworkAPI is checking "other_user_path" for incoming messages and rejects messages with "wrong" path. Maybe error in check. Maybe ZeroNet is just helping distribution optional files. See https://github.com/jaros1/Money-Network/issues/298#issuecomment-356643300

jaros1 commented 6 years ago

Workflow:

torando w2 sends a money transaction status message 619fa5df4d-o.0000000000001 to torando w2
montreal mn session tries to read 619fa5df4d-o.0000000000001 message from torando w2 (OK)
montreal mn session timeout for read 619fa5df4d-o.0000000000001 message (OK)
montreal mn sessions sends a waiting_for_file message to torando (Not OK). It must be montreal w2 session that should send a waiting_for_file message to torando w2 session.

jaros1 commented 6 years ago

Fixed. Minor change in message_demon in MoneyNetworkAPI.js

jaros1 commented 6 years ago

Continued issue 298 test 7. Still hanging money transaction ...

issue298-test7a-torando-mn.log issue298-test7a-torando-w2.log issue298-test7a-montreal-mn.log issue298-test7a-montreal-w2.log

Still sending waiting_for_file messages from MN. client variable was not set correct in message_demon. Fixed

jaros1 commented 6 years ago

Issue 298 test 8. Looks OK. Todo. check for waiting_for_file messages from MN sessions.

issue298-test8a-montreal-w2.log issue298-test8a-montreal-mn.log issue298-test8a-torando-mn.log issue298-test8a-torando-w2.log

jaros1 commented 6 years ago

Tested OK. No "sending waiting_for_file notification to other wallet" messages in MN logs