Fix onAnonDataReq() always sending response as flood #1485
+5
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
Converted to draft, @ripplebiz pointed out that the handlers are meant to do this so I'll investigate further. I'll also remember to include room server and sensor next time 🤦♂️ |
oltaco
force-pushed
the
fix-anonreq-reply
branch
from
f3b6167 to
d99ec2f
Compare
oltaco
force-pushed
the
fix-anonreq-reply
branch
from
d99ec2f to
7c30bd5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes onAnonDataReq() always sending response as flood, even when repeater login etc was sent with a path or direct.
Confirmed that now direct and pathed logins will respond via path instead of flood, and flood logins still reply with flood.