httpheaderprovider
Advanced tools
httpheaderprovider - npm Package Compare versions
Comparing version 0.3.0 to 0.3.1
| { | ||
| "name": "httpheaderprovider", | ||
| "version": "0.3.0", | ||
| "version": "0.3.1", | ||
| "description": "Replacement for HttpProvider from web3.js which allows headers to be set", | ||
@@ -5,0 +5,0 @@ "main": "lib/index.js", |
| # HttpHeaderProvider - A Replacement Web3.js HttpProvider supporting custom HTTP Headers | ||
| This module can be used in place of `HttpProvider` from web3. | ||
| This module can be used in place of `HttpProvider` from [web3.js](https://github.com/ethereum/web3.js/). | ||
@@ -7,3 +7,3 @@ Once in place, the constructor offers a `headers` parameter that is a `key/value` object that has the headers to be set. | ||
| ## Purpose | ||
| The [`JSON-RPC`](https://github.com/ethereum/wiki/wiki/JSON-RPC) endpoint on an [Ethereum client](https://geth.ethereum.org) provide no authentication boundary. All validation is based upon the presence of a signed transaction or not. | ||
| The [`JSON-RPC`](https://github.com/ethereum/wiki/wiki/JSON-RPC) endpoint on an [Ethereum client](https://geth.ethereum.org) provides no authentication or authorization boundary. All validation happens after the client receives the reqeust and processes it, and true validation is based upon the presence of a signed transaction or not. | ||
@@ -16,7 +16,6 @@ With no protection at [layer 7](https://www.nginx.com/resources/glossary/layer-7-load-balancing/), this does pose a DoS risk vector. However, by putting a simple layer 7 proxy in front of Geth or whatever Ethereum client is being used that has the RPC endpoint open, that proxy could validate something simple like an API key or potentially an OAuth token. | ||
| #### Authorization | ||
| API Managment employs simple "token" or API Key approach in addition to OAuth bearer tokens that can be granted by Azure Active Directory, then added to the `Authorization : Bearer <token>` header. | ||
| API Managment employs simple `token` or API Key approach in addition to OAuth bearer tokens that can be granted by Azure Active Directory, then added to the `Authorization : Bearer <token>` header. | ||
| #### Throttleing | ||
| API Manaement can also throttle based on various policies, as well as authorize only certiain calls to specific clients, all through a configuration oriented approach. | ||
| # Usage and Approach | ||
@@ -23,0 +22,0 @@ |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by0.69%
20242
Worsened metrics
- Number of lines in readme file
- decreased by-1.27%
78