mitmweb 2.0.1 not working under Chrome 58

Steps to reproduce the problem:

1. start mitmweb
2. open the mitmweb web page in Chrome 58
3. no visible content

Any other comments? What have you tried so far?

It’s working fine under Chrome 57.0.2987.133 and Firefox I was able to show the interface by playing with the answers from http://stackoverflow.com/questions/31211359/ (added the meta tag from http://stackoverflow.com/a/35273628/19756 to the index.html template), but I still have some warnings in the console:

WARNING:tornado.access:404 GET /static/vendor.js.map (10.162.60.254) 0.00ms WARNING:tornado.access:404 GET /static/app.js.map (10.162.60.254) 0.00ms WARNING:tornado.access:404 GET /static/vendor.css.map (10.162.60.254) 1.00ms WARNING:tornado.access:404 GET /static/app.css.map (10.162.60.254) 1.00ms

System information

Chrome 58.0.3029.81 (64-bit)

mitmweb --version Mitmproxy version: 2.0.1 (release version) Python version: 3.5.2 Platform: Windows-8.1-6.3.9600-SP0 SSL version: OpenSSL 1.1.0e 16 Feb 2017 Windows version: 8.1 6.3.9600 SP0 Multiprocessor Free

[mhils]

Ok, I checked and Chrome does follow the spec: ws://* does not specify a port, so it actually expands the expression to the default port (ws://*:80), which does not match our ws://localhost:8081/. The short-term workaround is to run mitmweb on port 80 (--wport). We’ll push a patch release nonetheless.

[spwert]

Forced page reload did the trick, thanks!