Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing documentation around remote middleware #459

Closed
benjih opened this issue Mar 14, 2017 · 1 comment
Closed

Missing documentation around remote middleware #459

benjih opened this issue Mar 14, 2017 · 1 comment

Comments

@benjih
Copy link
Contributor

benjih commented Mar 14, 2017

Having a look at the documentation, middleware makes no reference to running it remotely.

We should add this as well as an explanation as to why you might do this over the standard way of running middleware.

You can configure middleware to run remotely. To do this, you need to provide a URL as middleware.

hoverctl middleware --remote <middleware-url>

When implementing middleware in this way, Hoverfly will POST the same RequestResponsePair JSON it would send to stdin for standard middleware. Hoverfly will then expect a 200 response will the same RequestResponsePair JSON it would read from stdout from standard middleware.

@benjih
Copy link
Contributor Author

benjih commented Aug 25, 2017

There is now documentation for HTTP middleware.

@benjih benjih closed this as completed Aug 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant