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
I'm using this library to interact with Bitcoin node developed by parity-tech (link). And I have problem to connect parity-bitcoin node because it requires header value 'Content-Type' with 'application/json'.
After testing locally I've found out that this library uses request header 'Content-Type' value as 'application/x-www-form-urlencoded'.
Is this intended behavior? I think it would be better to set 'Content-Type' value as 'application/json' explicitly for supporting parity-bitcoin and following jsonrpc over HTTP header value suggestion
The text was updated successfully, but these errors were encountered:
I'm using this library to interact with Bitcoin node developed by parity-tech (link). And I have problem to connect parity-bitcoin node because it requires header value 'Content-Type' with 'application/json'.
After testing locally I've found out that this library uses request header 'Content-Type' value as 'application/x-www-form-urlencoded'.
Is this intended behavior? I think it would be better to set 'Content-Type' value as 'application/json' explicitly for supporting parity-bitcoin and following jsonrpc over HTTP header value suggestion
The text was updated successfully, but these errors were encountered: