You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
![]() |
4 years ago | |
---|---|---|
embedded | 4 years ago | |
forward | 5 years ago | |
helper | 5 years ago | |
legacy | 5 years ago | |
mirror | 5 years ago | |
reverse | 5 years ago | |
LICENSE.md | 5 years ago | |
README.md | 5 years ago | |
build-install-all.sh | 5 years ago | |
overview.png | 5 years ago | |
overview.uxf | 5 years ago |
README.md
About
The goal of this project is to bypass the limitations caused by ISPs blocking incoming connections.
To do so, the proxy reverse
is created.
reverse
sends Ride
objects to another proxy, which is called forward
.
forward
waits for a request from the user
,
and inserts the request into the Ride
object received form reverse
.
The Ride
object is then sent back to reverse
.
reverse
subsequently forwards the request contained in the Ride
object to the app
.
Upon recieving a reply with data from app
, reverse
will forward this data to forward
,
which in turn will finally forward it to the user
.
Overview
What works:
- Forwarding GET requests (including HTTPS).
What does not work:
- Handling 301 (Moved Permanently).
- Forwarding PUT requests - if needed, the logic might be quickly added to
doPut
inforward
. - The
forward.war
has issues - meanwhile runforward
embedded with Jetty.
Demo
Run / Deploy
How to Run / Debug
com.olexyn.misp.embedded.RunAll.main()
How to Deploy
- Set the URIs in code.
- Build (e.g. with
build-install-all.sh
) - Put the generated
forward-0.1.war
in a servlet container (e.g. Jetty). - Launch the
reverse-0.1.jar
on your host.