[Question] API I/O Spec? #11
Comments
|
Dumping endpoints simply take raw `WRR` dumps as request bodies.
See `submitHTTPOne` function in `extension/background/core.js`.
Another would be stream processing the data to redact PII, tokens, passwords, and sensitive information in an attempt to see how close to safe I can make dumps from authenticated, logged in, browser sessions.
Hmm, that's a good idea.
`hoardy-web serve` could be made to strip <head>/<meta> tokens, hidden form fields, and simply ignore anything with `/login/` in the URL.
Or, maybe, a better way would be to put such `WRR`s into a separate directory and add `hoardy-web strip` command that would censor `WRR` -> `WRR` in various ways.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I kind of want to implement my own API for accepting dumps (Not really for replaying), and writing them as WRR files.
Various reasons, but playing around is one. Another would be stream processing the data to redact PII, tokens, passwords, and sensitive information in an attempt to see how close to safe I can make dumps from authenticated, logged in, browser sessions.
I'm not a python dev, far from it. Is there a spec that defines the I/O format for the data dumping endpoint so I can implement my own?
The text was updated successfully, but these errors were encountered: