Alexander Prinzhorn

> Yup! Taking this one step further: It would be really cool if we could have mitmproxy listen on port 8080 as an HTTP proxy, port 1080 as a SOCKS...

I can't reproduce this on Ubuntu (I tried the main branch). I can access http://127.0.0.1:8081/ in both Firefox and Chromium and don't see an error in the console. Are there...

> but got it fixed cleaning the browser cache That sounds plausible, does that fix it @taylorlennon? If so then that's still confusing, because we send an `Etag` header and...

I never looked at it this way, makes sense. I don't think this applies to `basename` though? > make it overly easy to hide that mitmproxy is intercepting a connection...

Great, I'll reopen this and will look into it within the next weeks or years :smile: . Apart from the hardcoded `mitmproxy` basename in mitmweb HTML this should be somewhat...

I do have a wish list and I think some of these things are both interesting and challenging enough for GSoC, but not too unrealistic: * ~**async addon hooks** with...

Thanks for reporting! Can you try with this script? ```py def responseheaders(flow): flow.response.stream = flow.response.headers.get('content-type', '').startswith('text/event-stream'); ``` ```sh mitmdump -s sse.py ``` SSE uses chunked response and mitmproxy will buffer...

I'm marking this as a feature request, maybe we should stream `text/event-stream` by default? @mhils Edit: I mean streaming it by default would at least make it work, but it...

I think the pages and resources are simply cached by the browser and hence the requests will never reach mitmproxy? There might also be some client side routing involved, so...

I think your steps above are also missing something. I assume between 2 and 3 you also configure the browser/device to actually use the proxy? Or how else would that...