public
/
misp
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Reverse-Proxy for exposing the Host through a Firewall.
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.
78 Commits
5 Branches
0 Tags
5.3 MiB
 
 
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '2aa1eb7339'
${ noResults }
Go to file
Ivan Olexyn 2aa1eb7339
~ release. 		5 years ago
embedded ~ release. 5 years ago
forward ~ release. 5 years ago
helper ~ release. 5 years ago
legacy ~ cleanup. 5 years ago
mirror ~ release. 5 years ago
reverse ~ release. 5 years ago
LICENSE.md + servlets interact 5 years ago
README.md ~ release. 5 years ago
build-install-all.sh ~ overhaul for simple debugging. 5 years ago
overview.png + querying for supply implemented. 5 years ago
overview.uxf ~ release. 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 have an adapter or reverse-proxy reverse. It sends Rides to a forward-proxy servlet forward. This servlet waits for a request, and fills the Ride with the request. reverse can then forward the request 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 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 in forward.
  • The forward.war has issues - meanwhile run forward embedded with Jetty.

Demo

Demo

IMAGE ALT TEXT


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.