Maximilian Hils

> I never looked at it this way, makes sense. I don't think this applies to `basename` though? Agreed, basename is fine. > I'd be totally fine with if you...

One workaround here is to update `flow.request.scheme` (or `flow.request.url`) in the `request` or `requestheaders` hook to use `http` instead of `https`. I do agree though that we have at least...

Streamed bodies are currently not captured, that would definitely need to change if we want to enable it by default.

Unfortunately no, because some folks rely on the fact that mitmproxy captures _everything_ that's going on between client and server (think of forensic use cases). Discovering after the fact that...

Looks like we just need to catch the error here. This should be an easy fix, PRs welcome! 😃

Thanks for migrating this here, @iTosun! Yes, this is something we'd be happy to have support for, mitmproxy/mitmweb#10 has the relevant discussion. Unfortunately it's not quite trivial, if someone wants...

This should be fixed in 8.1.1.

> `content_view_lines_cutoff` is only for mitmproxy ui, I guess we need to introduce a new option for the dumper and default to `0` (dump everything) I guess? We should make...

Could you please explain why this is necessary? We do `chown -R mitmproxy:mitmproxy ~/.mitmproxy` in our entrypoint, which should resolve all permission errors.

Superseded by https://github.com/mitmproxy/mitmproxy/pull/5550