Forgot to update the second map; it should be:
map $is_admin$request_method $admin_required {
"0GET" 0;
"0HEAD" 0;
"0OPTIONS" 0;
"~1.*" 0;
default 1;
}
Patrick
On 2019-06-19 11:02, Patrick wrote:
> On 2019-06-18 16:41, Matthias Müller wrote:
> > 1) Permit POST, PUT if the r
On 2019-06-18 16:41, Matthias Müller wrote:
> 1) Permit POST, PUT if the request matches a trusted IP address OR
> Basic auth credentials (either-or)
Something like this will work:
map $remote_addr $is_admin {
1.2.3.4 1;
default 0;
}
map $is_admin$request_method $admin_required {
"GET"
Given what that post states and since openssl 1.1.1 hit 18.04 the other
day, i'd assume the next build would be based off of 1.1.1? While i use
nginx, i terminate SSL at HAProxy, and that is what occurred last week.
On Tue, Jun 18, 2019 at 2:17 PM Zeev Tarantov wrote:
> The openssl package for
On Tue, Jun 18, 2019 at 03:33:32PM +, Suleman Butt wrote:
Hi there,
> location ~ ^/proxy/(.*)$ {
> proxy_pass http://localhost:3000/$1$is_args$args;
> I just get this in the browser:
>
> [cid:image002.png@01D525FB.F2988B00]
>
> Any suggestion what is wrong in my docker file or
The openssl package for Ubuntu 18.04 (bionic) was recently upgraded to
openssl 1.1.1 with TLS 1.3 support, but the nginx binary provided in the
apt package repository http://nginx.org/packages/ubuntu was compiled with
openssl 1.1.0 and does not support TLS 1.3 even when system openssl is
1.1.1.
(T
I setup my own error_page for 400 but it doesn't seem to be honored. The
default page still is returned when client failed to provide certificate.
Any ideas?
< HTTP/1.1 400 Bad Request
< Date: Tue, 18 Jun 2019 17:50:04 GMT
< Content-Type: text/html
< Content-Length: 230
< Connection: close
<
400
On Mon, Jun 17, 2019 at 11:24:17PM +, Vivek Solanki wrote:
Hi there,
> location /media {
> rewrite ?/media(.*) /$1 break;
> proxy_pass $upstream_endpoint/media;
> }
> Requests will come like
> https://abc.example.com/media/movie/bollywood/action/wallpapar
>
> Please help me out in
Hi NGINX team, do we have sample script or somebody that already did the
auto retrieval script of the CRL on a regular basis ?
Before re-inventing the Wheel, i was wondering if something exists.
My idea was to wget the file, swap the file, run nginx -t
If 0 = we reload nginx
if >0 = we swap back t
I would like to constrain HTTP access (PUT, POST) to an NGINX server
for specific locations.
There are two cases:
1) Permit POST, PUT if the request matches a trusted IP address OR
Basic auth credentials (either-or)
2) Permit POST, PUT if the request matches a trusted IP address AND
Basic auth cr
