I am looking for a asynchronous proxy server, that will allow me to tunnel requests over a message queue to a server that is behind a firewall. I do not want to allow incoming connections to the server from the internet.

I was thinking of running a proxy server on an internet exposed server, which will push the request to a message queue (Redis / RabbitMQ). A client instance running on the internal server will fetch the request from the queue and replay it locally, and save the response back into the queue.

The proxy server on the internet exposed server will fetch the response from the queue and pass it on the the original requester.

Does goxyq support the above use case?

I think this project is what I'm looking for, but I can't quite tell.

I'm looking to proxy HTTP requests from a backend server to an API, but rate-limit them. It looks you've purpose-built this for exactly that purpose. If I'm reading (skimming, actually) the code correctly, the queuing system ensures that only a single request is in-flight at any given time for any queue (queues are created for every different value of configured QueueAtrribute), but sends them out back-to-back. Requests with a header matching one in HeaderBypass do not get queued and are simply sent out as soon as they are received.

Is that all correct? In my specific case, I would need to implement a delay between each request (I'm using this to avoid hitting a rate-limit on a 3rd party API) - I would be willing to submit a PR for this, or at least attempt one, provided 1) you're open to this, 2) my Go doesn't fail me 3) it's not too complicated. I would ideally like to queue requests to several 3rd party APIs, but don't mind running multiple instances of goxyq if need be. Do you think goxyq is the right solution here?

Thanks for publishing goxyq and for taking the time to read this (and hopefully answer!)