So, I've got a need for a reverse proxy where first it tries server A;
if it gets a 404 from server A it should try server B, and then just
return whatever happens with server B.
I've got this config so far:
location /_nginx_/ {
internal;
root /var/www/localhost/nginx;
}
location
On 2019-05-03 09:33, Duke Dougal wrote:
> > The secret, expiry, and uri are the same from md5 generation to the
> > cURL request?
>
> Could you please explain the question further? - I’m not sure how to check
> this thanks.
Sure. Use shell variables -- e.g.
#!/bin/bash
secret="w00w00"
uri="/html
On 1 May 2019, at 10:56 am, Patrick <201904-ng...@jslf.app> wrote:
On 2019-05-01 10:06, Duke Dougal wrote:
Any further ideas?
1) The URL returns 200 when the secure-link config is disabled?
url="http://127.0.0.1/html/index.html";
curl -sI $url
2) The secret, expi
Is there an equivalent of max_fails
(http://nginx.org/en/docs/http/ngx_http_upstream_module.html#max_fails) if
I'm using proxy_pass without an upstream block?
E.g.
http {
server {
resolver 10.0.0.2 valid=5s;
set $upstream_server http://foo.bar:80;
location ~* \.(html)$ {
Hi,
thx for your reply. You say
> [...] To post to
> the mailing list, you have to be subscribed [...]
I am subscribed.
I did it per mail to nginx-requ...@nginx.org so mailman knows my envelope-from
and my from-header.
And I can talk to nginx-request@ without problems.
_
