https://github.com/domiii/proxy-play
A very basic HTTP proxy to allow us (later) play with injection.
https://github.com/domiii/proxy-play
Last synced: 12 months ago
JSON representation
A very basic HTTP proxy to allow us (later) play with injection.
- Host: GitHub
- URL: https://github.com/domiii/proxy-play
- Owner: Domiii
- License: apache-2.0
- Created: 2020-08-05T16:51:04.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2021-05-05T08:25:43.000Z (about 5 years ago)
- Last Synced: 2025-03-11T01:52:59.246Z (over 1 year ago)
- Language: JavaScript
- Size: 128 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
Acts as a proxy to inject [Dbux](https://github.com/Domiii/dbux) into all scripts of any website, before they execute in the browser, thereby allowing to analyze any website's scripts with Dbux.
# Usage
1. Install the [dbux-code](https://github.com/Domiii/dbux/dbux-code) VSCode extension.
1. Open VSCode and [`start the Dbux Runtime Server`](https://github.com/Domiii/dbux/dbux-code#dbux-runtimeserver).
1. `yarn install`
1. `yarn start`
1. Go to: http://localhost:8080/https://stackoverflow.com
1. Analyze your files!
# How does it work?
Instrumentation primarily happens in [src/transforms/javascriptTransform.js](src/transforms/javascriptTransform.js) and [src/transforms/instrument.js](src/transforms/instrument.js).
# TODO
* gather urls that are not instrumented (being sent straight to the domain, not under any child route)
* store files, so we can actually "go to code", "select traces" etc.
* caching (because instrumentation is *slow* on large files)
* whitelisting of "too large files"
* work around CSP