https://github.com/dr-dream/rest-to-rest-proxy

Quarkus/Camel based proxy to pass http requests to remote agent
https://github.com/dr-dream/rest-to-rest-proxy

camel kotlin quarkus vertx websocket

Last synced: about 1 month ago
JSON representation

Quarkus/Camel based proxy to pass http requests to remote agent

• Host: GitHub
• URL: https://github.com/dr-dream/rest-to-rest-proxy
• Owner: Dr-Dream
• Created: 2022-10-19T16:29:26.000Z (about 2 years ago)
• Default Branch: main
• Last Pushed: 2024-06-28T11:01:00.000Z (5 months ago)
• Last Synced: 2024-09-26T07:40:12.198Z (about 2 months ago)
• Topics: camel, kotlin, quarkus, vertx, websocket
• Language: Kotlin
• Homepage:
• Size: 260 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Enterprise reverse proxy

Consumes incoming HTTP requests and passes it to the remote agents through WebSocket.

## Disclaimer

This project created only for academic proposes and not supposed to be run on production environments.

Using that code or binaries you should accept all security and performance risks.

## Idea

For example, developer, have notebook and working remotely without any "white" IP (public accessible).

But you have a remote host with public static IP and don't have. So what to do?

Let's imagine you run http service which accepts all http traffic and passes it back to you by any channel with all

payload and headers. As soon you will get it you do the same request and to localhost to your "development" service, 

get your response and passes it all back to the requester.

## How it works

Agent is and service that connects to the GW and registers specific path to accept traffic. All exchange between

AGENT and GW goes through Websocket

```mermaid

sequenceDiagram

    participant DEVELOPMENT SERVICE

    participant AGENT

    participant GW

    participant CLIENT

    AGENT ->> GW: Websocket: SubscribeMessage (Registering path endpoint /someAgentPath)

    GW ->> AGENT: Websocket: SubscriptionMessage with subscription key

    loop 

        AGENT -->> GW: Websocket: KeepAlive Ping

        GW -->> AGENT: Websocket: KeepAlive Pong

    end

    CLIENT ->> GW: Http request on /someAgentPath

    GW ->> AGENT: Websocket: HttpRequestMessage (with headers and payload)

    AGENT ->> DEVELOPMENT SERVICE: Http request (Host replaced)

    DEVELOPMENT SERVICE ->> AGENT: Http response

    AGENT ->> GW: Websocket: HttpResponseMessage (with headers and payload)

    GW ->> CLIENT: Http response

```

To start

1) Compile and start gw which creates an WS for agent connections and start accepting http traffic

2) Configure and start agent which h will connect to WS of gw and binds to specific to agent endpoint

3) All traffic coming to that endpoint will be passed to agent without changes

4) Agent getting traffic changes host on incoming http request and passes it to bound local address.