vertx-http-proxy
vertx-http-proxy copied to clipboard
eclipse-vertx
vertx http proxy
We should have the ability to provide some contextual data when handing over a request to the proxy. This data should be accessible to all the different proxy components (e.g....
As of 4.5, it is possible to build a proxy server with different backend using a combination of `vertx-http-proxy`, `vertx-web` and `vertx-web-proxy` tools. As an example: https://github.com/tsegismont/http-proxy-playground/ Users should be...
Verify caching handles all cases defined in https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching It seems the caching implementation takes into account resources when the backend responds with headers defined by the modern specs. Some backends...
We should let users decided (e.g. by providing a set of paths in configuration) which resources shall be cached instead of enabling caching for all resources. Besides, it should be...
Depends on #67 Storing cached resources in an external system allows for sharing content between several proxy servers. Redis is popular and we already have a Vert.x Redis Client.
When the cache is enabled, cached content is stored on heap memory. Users should be able to choose between different storage implementations.
All Vert.x stack projects should have a small example in the [vertx-examples](https://github.com/vert-x3/vertx-examples) repository.
### Version 4.3.8 ### Context I investigated an issue, where websocket upgrades were failing. We have a service handling websockets living behind the `vertx-http-proxy`. This service is living on a...
- [ ] path (e.g. prefix addition or removal) - [ ] query (e.g. transform query param into path param) - [ ] headers/trailers (filtering and modification) - [ ]...
### Version Since [`originRequestProvider`](https://vertx.io/docs/apidocs/io/vertx/httpproxy/HttpProxy.html#originRequestProvider-java.util.function.BiFunction-) runs after pre-request interceptors, there is no way to pass the `ProxyContext` to perform routing on the based on the modified request. `originRequestProvider` only has context...
