Repository navigation
Add a send command for raw client messages - #17
Merged
Merged
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
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.
noz send <url> <json>sends one raw client message and prints every relay reply verbatim until the one that ends it (EOSE, CLOSED, COUNT, OK or NOTICE). With--sec <k> --authit answers a NIP-42 challenge and re-sends the message once authenticated, without printing the auth-required rejection that preceded it.This covers what the flag-built
reqandcountcannot express, such as multi-filter REQs,limit: 0, and reads of AUTH-gated data, so relay test suites can assert on them.The auth acknowledgement is matched by the auth event's id, replies to the first unauthenticated send are dropped once the auth event is out, and an auth-required rejection that arrives before the challenge (OK or CLOSED) does not end the run. The relay-tier suite covers a two-filter REQ and a COUNT through
send, and a newintegration_auth.sh(run in CI against a relay with AUTH available) covers a protected EVENT and a REQ with--auth.