diff options
author | Maximilian Hils <git@maximilianhils.com> | 2014-01-31 01:44:55 +0100 |
---|---|---|
committer | Maximilian Hils <git@maximilianhils.com> | 2014-01-31 01:44:55 +0100 |
commit | 30a44cbb41fab51a30e609ba6318e1e8c062f73a (patch) | |
tree | 3a2585a3393ee2469d7d70b3635ae5a35cee101d /libmproxy/protocol/http.py | |
parent | 6ce1470631e843bef926d9fee5c2ad1f359dc0ac (diff) | |
download | mitmproxy-30a44cbb41fab51a30e609ba6318e1e8c062f73a.tar.gz mitmproxy-30a44cbb41fab51a30e609ba6318e1e8c062f73a.tar.bz2 mitmproxy-30a44cbb41fab51a30e609ba6318e1e8c062f73a.zip |
fix server reconnect
Diffstat (limited to 'libmproxy/protocol/http.py')
-rw-r--r-- | libmproxy/protocol/http.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/libmproxy/protocol/http.py b/libmproxy/protocol/http.py index 11735ec0..fcfc53b8 100644 --- a/libmproxy/protocol/http.py +++ b/libmproxy/protocol/http.py @@ -988,7 +988,7 @@ class HTTPHandler(ProtocolHandler): self.c.channel.ask("error" if LEGACY else "httperror", flow.error if LEGACY else flow) else: - pass # FIXME: Is there any use case for persisting errors that occur outside of flows? + pass # FIXME: Is there any use case for persisting errors that occur outside of flows? if code: try: |