Hi Francis and and Reinis,
many thanks for the ideas and hints!
At least, I feel assured, that my idea seems to be not completely
unreasonable ;)
Crawling would be no necessity, assuming that the first client will make
'all' the requests to populate the cache.
I will try my luck.
Cheers and th
> "caching reverse proxy" is what nginx is built for.
>
> "rewriting the body content" is not.
Well you can rewrite body with the sub module (
http://nginx.org/en/docs/http/ngx_http_sub_module.html )
The only caveat is that the module doesn't support compression (gzip) and you
need to explic
On Wed, Feb 20, 2019 at 12:37:23PM +0100, Thomas Hartmann wrote:
Hi there,
> I would like to setup Nginx as a caching reverse proxy but with explicit
> requests in the URL and rewriting all subsequent requests
"caching reverse proxy" is what nginx is built for.
"rewriting the body content" is n
Hi all,
I would like to setup Nginx as a caching reverse proxy but with explicit
requests in the URL and rewriting all subsequent requests
Don;t know, if it really counts as reverse proxy and if it is
understandable, so an example ;)
For an original URL like
https://org.url.baz/user/repo/foo
