Skip to content

HTTP/2 does not handle killed requests #1084

@mhils

Description

@mhils
Steps to reproduce the problem:
  1. mitmdump -S test_replay --kill
  2. Open a website that is not contained in the replay file.
What went wrong?
127.0.0.1:50907: clientconnect
127.0.0.1:50906: clientconnect
127.0.0.1 GET https://news.ycombinator.com/ HTTP/2.0
 << Connection killed
Exception in thread Thread-2:
Traceback (most recent call last):
  File "c:\python27\Lib\threading.py", line 810, in __bootstrap_inner
    self.run()
  File "c:\users\user\git\mitmproxy\mitmproxy\protocol\http2.py", line 422, in run
    layer()
  File "c:\users\user\git\mitmproxy\mitmproxy\protocol\http.py", line 188, in __call__
    self.process_request_hook(flow)
  File "c:\users\user\git\mitmproxy\mitmproxy\protocol\http.py", line 356, in process_request_hook
    raise Kill()
Kill

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions