You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that mitmproxy-java is based on the mitmproxy-node as stated in the repo, but mitmproxy-node has not been maintained since long and I wonder if it is a potential issue for this project.
I found another node module node-http-mitm-proxy which is also being used by the appium-interceptor-plugin for capturing and modifying the request and response data, and it seems to be updated and maintained.
Is there a dependency of this project on mitmproxy-node or it is only stated in docs for reference to the original node module which formed the basis of this project. I would like to understand your point of view and also what do you think about using node-http-mitm-proxy to re-architecture this project.
This project doesn't depend on mitmproxy-node, but it copied the Python scripts that mitmproxy-node used in order to communicate with mitmproxy.
Rearchitectinng the project to use a newer dependency sounds fine to me. It seems like people are still interested in being able to run the process from Java.
Activity
Jonahss commentedon Apr 25, 2025
This project doesn't depend on mitmproxy-node, but it copied the Python scripts that mitmproxy-node used in order to communicate with mitmproxy.
Rearchitectinng the project to use a newer dependency sounds fine to me. It seems like people are still interested in being able to run the process from Java.