h2non / rocky Goto Github PK

Avoid this: https://github.com/h2non/rocky/blob/master/lib/proxy.js#L15

To incercept both request and response

• replay
• balance

Sometimes we don't wanna forward the request

proxy
  .get('/users/admin')
  .reply(401, { 'Content-Type': 'application/json' }, { message: 'Forbidden' })

Proposed at #28

Buffer all the body payload, then parse it properly, and finally expose it to the forward/replay middleware

Support both regexp and filter function

route.transformBodyRequest(transformer, { filter: /application/json/ })

route.transformBodyRequest(transformer, { filter: function () { ... } })

Would be awesome to make rocky installable via PM2,

I recently embedded a npm install procedure + start with PM2 to make possible to install software easily by doing something like that:

$ pm2 install <npm-package-name>

There is a small documentation about the system

Tell me if you are interested to build a module like that, I can make modifications on the PM2 configuration system and related.

Add test coverage!

Like with responses!

Probably a good fit could be:

route.useReplay(middleware)

This will make rocky more lightweight. Proposed name: rocky-cli

Split routing layer by host header

Currently that could be achieved using a middleware

Based on request headers and payload data (requires buffering it)

Better API docs, usage example and explanation (injected fields in request, inversion of control...)

• Keep consistency with other middleware layer

In some scenarios, once the stream has been consumed and therefore the buffer is empty, it's not possible to replay the request with the proper payload.

A nice-to-have feature. Could be useful to discern the proxy behavior according to some specific request headers/params.

The API may look like this:

proxy.get('/users/:id')
  .match('X-Version', /^1.*/)
  .forward('http://old.server')
  .match('X-Version', /^2.*/)
  .forward('http://new.server')

Alternative implementation, using internally the router middleware

proxy.get('/users/:id', { 'X-Version', /^1.*/ }, function () { ... })
  .forward('http://google.es')

Internally it should be implemented via middleware