We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I just tried out the program with a dump made with the current mitmproxy version 11.0.0
When I run the example like
mitmproxy2swagger -i <my-dump-file.mitm> -o api.json -p https://<removed>/api/v1
it defaults to HAR import and crashes with a UnicodeError
If I add
-f flow
the output is
"Flow file corrupted: mitmproxy 10.4.2 cannot read files with flow format version 21, please update mitmproxy."
Maybe you can add a warning to not use the current mitmproxy.
Some more info: When I manually update mitmproxy in the venv the code runs, but lists all endpoints as ignored.
The text was updated successfully, but these errors were encountered:
try to setup via pipx !
Sorry, something went wrong.
I just tried out the program with a dump made with the current mitmproxy version 11.0.0 When I run the example like mitmproxy2swagger -i <my-dump-file.mitm> -o api.json -p https://<removed>/api/v1 it defaults to HAR import and crashes with a UnicodeError If I add -f flow the output is "Flow file corrupted: mitmproxy 10.4.2 cannot read files with flow format version 21, please update mitmproxy." Maybe you can add a warning to not use the current mitmproxy. Some more info: When I manually update mitmproxy in the venv the code runs, but lists all endpoints as ignored.
I get the same issue. Also tried with pipx
Similar issue was fixed in #110
No branches or pull requests
I just tried out the program with a dump made with the current mitmproxy version 11.0.0
When I run the example like
it defaults to HAR import and crashes with a UnicodeError
If I add
the output is
Maybe you can add a warning to not use the current mitmproxy.
Some more info: When I manually update mitmproxy in the venv the code runs, but lists all endpoints as ignored.
The text was updated successfully, but these errors were encountered: