Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

API alternative #432

brettz9 opened this Issue Jun 15, 2013 · 2 comments


None yet
2 participants

brettz9 commented Jun 15, 2013


Was wondering your thoughts on allowing the proxy to act as a full superset of the http or https APIs (Server, ServerResponse) whereby the "proxy" could be a transparent go-between for existing server code and middleware?

My interests are:

  1. To avoid setting up listeners on different ports (and adding the code to do so) while still getting the benefits of middleware.
  2. To make the addition of middleware even easier by simply swapping the requiring of "http" or "https" with either:
    • a generic proxy module (in which case one would also need to change one's existing code by adding middleware callbacks at the end of createServer) OR
    • a reusable module already baking in some specific middleware (thereby avoiding the need to modify existing code at all--excluding changing require("http") to require one's module)

Maybe this doesn't fit into your scope, so if not, it appears one could at least do this while supporting your middleware module API...



indexzero commented Jun 15, 2013

You are right, this is not in our scope.

@indexzero indexzero closed this Jun 15, 2013

brettz9 commented Jun 15, 2013

K, thanks, I implemented my own version at https://github.com/brettz9/htteepee

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment