davechri-test
Advanced tools
Readme
ProxyAll is similar to Fiddler and Charles, but in addition to HTTP(S), it also can captures SQL, gRPC, MongoDB, Redis, Memcached, TCP, and log messages.
Features:
The ProxyAll has been tested with node versions v10.22.1, and v12.19.1. Version 10 or higher is recommended. Use nvm to install the appropriate node version.
$ cd ~/git/proxyall
proxyall$ npm install
proxyall$ npm run build
Usage: npm start [--listen [host:]port] [--listenHttps [host:]port]
Options:
--listen - listen for incoming http connections. Default is 8888.
--listenHttps - listen for incoming https connections.
Example: npm start -- --listen 8888 --listenHttps 9999
proxyall$ npm start
> proxyall@1.0.0 start /home/davechri/proxyall-proxy
> if ./scripts/noDir.sh ./build; then npm run build; fi; if ./scripts/noDir.sh ./client/build; then npm run build-client; fi; NODE_ENV=production node ./build/app.js
Listening on http: 8888
Open browser to http://localhost:8888/proxyall
Listening on https: 9999
Enter http://localhost:8888/proxyall in browser.
To capture HTTP and HTTPS messages, configure your browser to proxy HTTP/HTTPS messages to the ProxyAll. The default is to proxy HTTP messages to port 8888, and HTTPS messages to port 9999. This is how Firefox can be configured to proxy HTTP and HTTPS messages.
for chrome and chromium you can set the browser proxy using environment variables http_proxy and https_proxy.
$ http_proxy=http://localhost:8888 https_proxy://9999 chromium-browser
This section gives example on how to configure the ProxyAll. Clicking the settings icon in the upper right corner opens the Setting modal.
Both a forward and reverse proxy is supported for HTTP/HTTPS messages. Your browser must be configured to proxy HTTP/HTTPS messages to the forward proxy. See Configure Browser Proxy for more information on configuring your browser.
The reverse proxy can be used to transparently capture HTTP/HTTPS messages sent by backend services. The backend service is configured to send the HTTP/HTTPS messages to the ProxyAll. For example, a -search- microservice could be configured to send Elasticsearch messages to the ProxyAll by setting environment variables.
Example -search- microservice configuration:
ELASTIC_HOST=elasticsearch
ELASTIC_PORT=9200
Modified -search- micorservice configuration:
ELASTIC_HOST=proxyall # proxyall is the docker container host name
ELASTIC_PORT=8888 # proxyall HTTP port is 8888. Use 9999 for HTTPS.
An HTTP path is added to proxy HTTP requests to the elasticsearch host. All HTTP requests matching path /_search are proxied to the elasticsearch host on port 9200.
The SQL proxy can transparently capture SQL messages sent by backend microservices to a MySQL server.
Example microservice config file:
MYSQL_HOST=mysql
MYSQL_PORT=3306
Modified microservice config file:
MYSQL_HOST=proxyall # Proxy queries to the ProxyAll
MYSQL_PORT=3306
The ProxyAll is configured to proxy MySQL requests to the MySQL server:
The gRPC proxy can transparently capture gRPC HTTP/2 messages sent to backend microservices. Only unsecure connections are supported. Secure TLS support may be added in the future.
Example gRPC microservice config file:
GRPC_HOST=grpchost # gRPC host name
GRPC_PORT=12345 # gRPC port number
Modified gRPC microservice config file:
GRPC_HOST=proxyall # Proxy gRPC requests to the ProxyAll
GRPC_PORT=12345
The ProxyAll is configured to proxy gRPC requests to a microservice:
The MongoDB proxy can transparently capture MongoDB messages sent by backend microservices.
Example MongoDB microservice config file:
MONGO_HOST=mongodb # MongoDB host name
MONGO_PORT=27017 # MongoDB port number
Modified MongoDB microservice config file:
MONGO_HOST=proxyall # Proxy MongoDB requests to the ProxyAll
MONGO_PORT=27017
The ProxyAll is configured to proxy MongoDB requests to a microservice:
The Redis proxy can transparently capture Redis messages sent by backend microservices.
Example Redis microservice config file:
REDIS_HOST=redis # Redis host name
REDIS_PORT=6379 # Redis port number
Modified Redis microservice config file:
REDIS_HOST=proxyall # Proxy Redis requests to the ProxyAll
REDIS_PORT=6379
The ProxyAll is configured to proxy Redis requests to a microservice:
The TCP proxy can transparently capture TCP request/response messages sent by backend microservices. For example, the TCP proxy can be used to capture memcached messages.
Example Memcached microservice config file:
MEMCACHED_HOST=memcached # Memcached host name
MEMCACHED_PORT=11211 # Memcached port number
Modified Memcached microservice config file:
MEMCACHED_HOST=proxyall # Proxy Memcached requests to the ProxyAll
MEMCACHED_PORT=11211
The ProxyAll is configured to proxy Memcached requests to a microservice:
The Docker log proxy can capture log messages.
The ProxyAll is configured to capture Dockers log messages:
The ProxyAll dashboard is stated from the browser with URL http://localhost:8888/proxyall.
The recording of messages can be temporarily stopped, to allow time to examine the messages without the log wrapping.
Filtering allows you to find messages matching a search filter, and hide other messages. The entire message is search for a match. The filter may be case insensitive, case sensitive, a logical expression, or a regular expression.
Types of filters:
Boolean filters can use &&, ||, !, and parenthesis.
To resend an HTTP or HTTPS request, click on the icon next to the request to open a modal. Optionally modify the request body, and then click the send button. If the dashboard is not paused, the resent request should appear at the bottom of the dashboard request log.
Clicking on the camera icon will take a snapshot of the currently captured messages, and create a new snapshot tab. A snapshot tab may be exported to a file, and later imported again.
Multiple Dashboard instances can be opened in separate browser tabs, and all of the open Dashboards will record messages.
Each Dashboard instance keeps its own copy of the messages, so clearing or stopping recording in one Dashboard instance, does not affect another other Dashboard instances.
Certificates are managed by the node-http-mitm-proxy package.
Generated certificates are stored in proxyall/.http-mitm-proxy/certs/. The '/proxyall/.http-mitm-proxy/certs/ca.pem' CA certificate can be imported to your browser to trust certificates generated by the ProxyAll.
This code is licensed under the MIT License.
FAQs
ProxyAll: HTTP, SQL, gRPC... Debugging Tool.
We found that davechri-test demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The Python Software Foundation has secured a 5-year sponsorship from Fastly that supports PSF's activities and events, most notably the security and reliability of the Python Package Index (PyPI).
Security News
LDAPjs, an LDAP Client and Server API for Node.js, was decommissioned after its maintainer received an abusive email from a user, raising concerns about this form of abuse as a potential attack vector.
Security News
CISA launched a new project called Vulnrichment to enrich CVEs with details that help prioritize patching and mitigation efforts, as the NVD backlog of unenriched CVEs awaiting analysis surpasses 10,000.