-
Notifications
You must be signed in to change notification settings - Fork 29
Open
Description
Hey team Waves,
We've deployed a Waves mainnet node for which users of ours were planning to use the @waves/waves-transactions lib as a means to interact with the Waves blockchain. Since we control access to our node endpoints via an API key in the URL path, like waves-mainnet.provider.com/<API-key>/some/method, we're having issues using the library. What happens when an URL like waves-mainnet.provider.com/<API-key> is input as the nodeUrl parameter in the broadcast function, is that /transactions/broadcast overwrites the API key, and I've confirmed this through manual testing of my own.
So I'm now making this post to ask
- if the issue with path overwrite can be fixed
- or otherwise, if someone knows how work around this issue
Cheers,
J
Metadata
Metadata
Assignees
Labels
No labels