You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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, likewaves-mainnet.provider.com/<API-key>/some/method
, we're having issues using the library. What happens when an URL likewaves-mainnet.provider.com/<API-key>
is input as thenodeUrl
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
Cheers,
J
The text was updated successfully, but these errors were encountered: