| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
add SO_KEEPALIVE
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
asyncio: shift script reloading out of the tick event
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The granularity of mtime is surprisingly bad. Make the tests more robust
against this, and promote has_log back to a public method, now that we have a
few legitimate examples.
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The tick event is a nasty compromise, left over from when we didn't have an
event loop. This is the first patch in a series that explores moving our
built-in addons to managing coroutines on the eventloop directly for periodic
tasks.
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Fix pytest invocation errors
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix asyncio.call_soon -> asyncio.ensure_future
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
A grab-bag of mitmweb-related fixes
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Temporarily disable config saving until we can look at this more closely.
Config saving should:
- Only happen when explicitly requested by the user
- Only save changed values
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
See https://www.python.org/dev/peps/pep-0475/
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
Fixes #3067
|
|\ \ \ \ \
| | | | | |
| | | | | | |
asyncio: fix exit behaviour for console
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Add a master.run_loop function. This encapsulates our run behaviour so that
it can be used by implementations that need to manage their own run loop (like urwid).
- Shift crash exit message to the common core. I'm not convinced we really need
this, but if we want it it should be centralised.
- Clean up an extra exception that can be thrown by asyncio itself on "dirty"
termination after a mitmproxy crash.
|
|\| | | | |
| | | | | |
| | | | | | |
Ignore signal errors on windows + various fixes
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- Ignore the NotImplementedError raised by add_signal_handler on Windows.
- Entrypoints return an integer exit code, or None. Adjust our type annotations
and code to suit.
Fixes #3061
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Improve benchmarking
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This patch clarifies proxy shutdown, and specifies that the master.shutdown()
method is thread-save.
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- The benchmark addon now manages setting up and tearing down the backend and
traffic processes itself.
- Use wrk instead of hey. I get more consistent results with this tool, and hey
shows a strange tail-latency bump that seems artificial.
- Make termination behaviour simpler. The bencmark revealed a bug where .done
events were not called if the proxy was shut down by an addon.
|
|\ \ \ \
| | | | |
| | | | | |
fix Python 3.6 variable type annotations #3053
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Handling user script's exceptions, fix #2839
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
[requires.io] dependency update on master branch
|
| | | | | | | |
|
| | |/ / / /
| |/| | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
readfile fixes
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes #3051
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* Add a readfile_filter option that filters flows on read.
* Adjust test suite for asyncio.
* Add asynctest as a dev dependency.
|
| | | | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
fix example filename
|
|/ / / / / |
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
asyncio consolidation
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There are a few reasons for this. First, logs are now async, and can be called
at any time. Second, the event loop is thread local, so there can only ever be
one master per thread. These two things together completely obviate the need
for a handler context.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now that logs are async, using this call is almost always a mistake. Signal
this by making it semi-private. The method may go away entirely down the track.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Logs are now asynchronous, with a log entry pushed onto the event loop for
handling. To support this, the test mechanism grows an await_log method that
waits for a log entry to appear.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Instead, we just schedule coroutines directly onto the core loop.
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
added option to export request as httpie command
|
| | |_|/
| |/| | |
|
|\ \ \ \
| | | | |
| | | | | |
A unified handler for user's scripts exception
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
fixing 2837, added test
unified-function
deleting the wrong commit
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Remove socket listen backlog constraint
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I have no idea why we did this, but the default value is 128, and setting it
this low drops connections under conditions our users can reasonably be expeted
to reach.
|