Use a IProxyListener instead of a IHttpListener, fixes #5 #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
Is there any good reason to use a IHttpListener instead of a IProxyListener? Don't we want to only modify messages coming from the browser anyway?
This is an attempt to fix #5 by implementing a IProxyListener instead of a IHttpListener.
An alternative would be to still use IHttpListener but use the toolFlag value to decide if we want to process the message or not. The "advantage" of using the IProxyListener is that it allows the users to see both the original and the edited request in the proxy tab.