Thanks for this Gustaf. We'll reintroduce the 2 virtual servers.
Many thanks for all your help and hope you have a good Christmas.
Regards,
David
On Wed, 23 Dec 2020 at 13:17, Gustaf Neumann wrote:
>
> > Is there a defined way to cancel an upstream proxy request from within
> > the
Is there a defined way to cancel an upstream proxy request from within
the ::revproxy::upstream filter?
Inside the URL rewrite callback, one can decide based on all context
info, whether to forward to A or to B. However, one cannot decide whether
to forward or not, i.e. calling
Is there a defined way to cancel an upstream proxy request from within the
::revproxy::upstream filter?
This is the case I can't quite see a way forward with..
GET /folder1/page.html
when requested via port 443 we would want to reply via fastpath delivery
with no proxying.
when via port 8443 we
On 21.12.20 10:58, David Osborne wrote:
As far as I can remember, the multiple servers are to make routing
more convenient.
well, it is not the main purpose of multiple servers :)
However, with the changes of yesterday, your use case should work just fine.
I'm guessing I could be using
Thanks Gustaf,
As far as I can remember, the multiple servers are to make routing more
convenient.
For example, on port 443 we don't want to proxy /somefolder* to the
backend, but on port 8443 we always want to proxy to a backend.
Plus, /tcl* requests on port 443 would be proxied to a different
On 18.12.20 17:43, David Osborne wrote:
When the request arrives via server1/nsssl1 on port 443 everything
seems fine.
But when the requests comes in on server2/nsssl2 on port 8443, we get
the error:
[18/Dec/2020:16:33:00][28278.7f80e7635700][-socks-] Error: channel
"conn46" does not
Hi,
Thanks for your help on the segfaults last week. I've now built and
installed NaviServer at HEAD and things are much more stable now.
A knock on effect is our reverse proxy code no longer works. It was a
custom version of your revproxy code which wasn't as up-to-date. So we're
now attempting
