Hi
Not sure where to put this.
But I would like to have the ability to add client cert required any where
on the URI tree
so
www.abc.com.au/ you can access with out a cert but
www.abc.com.au/private/ you need a cert
www.abc.com.au/public/ no cert needed
A
__
In the current setup, I have
location / {
...
bunch of stuff
...
proxy_pass http://upstream.server;
}
Instead of duplicating the whole location block, can we do something like
location @http | / {
...
bunch of stuff
...
proxy_pass http://upstream.server;
}
On Wed, J
Hello!
On Wed, Jul 25, 2018 at 11:37:20AM -0700, Frank Liu wrote:
> I tried:
>
> error_page 497 $request_uri;
>
> It is kind of working, and I get the correct content/code back, but the
> response header is still has 400:
>
> HTTP/1.1 400 Bad Request
>
> My use case has nginx as a reverse pro
I tried:
error_page 497 $request_uri;
It is kind of working, and I get the correct content/code back, but the
response header is still has 400:
HTTP/1.1 400 Bad Request
My use case has nginx as a reverse proxy, and the real response code from
upstream is dropped though the response body and oth
I just tried it quickly. nginx gives 400 instead of 497 when I connect as
http to a ssl virtual host.
server {
listen 8443 ssl;
server_name localhost;
ssl_certificate /opt/nginx/ssl/localhost.crt;
ssl_certificate_key /opt/nginx/ssl/localhost.key;
ssl_session_cacheshare
Thanks Maxim!
Is there a way to tell nginx to treat 497 as no error, and continue normal
processing?
On Wed, Jul 25, 2018 at 8:14 AM, Maxim Dounin wrote:
> Hello!
>
> On Wed, Jul 25, 2018 at 07:46:49AM -0700, Frank Liu wrote:
>
> > Stream servers can now do ssl and non-ssl on the same port:
> >
Hello!
On Wed, Jul 25, 2018 at 07:46:49AM -0700, Frank Liu wrote:
> Stream servers can now do ssl and non-ssl on the same port:
> https://www.nginx.com/blog/running-non-ssl-protocols-over-ssl-port-nginx-1-15-2/
>
> Can this be added to http virtual hosts as well?
> If ssl is on a listening port
Stream servers can now do ssl and non-ssl on the same port:
https://www.nginx.com/blog/running-non-ssl-protocols-over-ssl-port-nginx-1-15-2/
Can this be added to http virtual hosts as well?
If ssl is on a listening port and client doesn't send ClientHello, can
nginx fallback to use normal http? Ma
I'm about 98% sure it is returning a 401 but I'm going to do some more
research.
I don't think we did anything too dumb
proxy_cache_valid 200 301 302 404 3m;
proxy_cache_use_stale error timeout updating invalid_header http_500 http_502
http_503 http_504;
This is kind of what is confusing me bu
Hello!
On Wed, Jul 25, 2018 at 01:14:29PM +, Friscia, Michael wrote:
> If the upstream server returns a 401 response I want to make
> sure Nginx serves the response. Right now it is serving the
> stale version. What happened is that the upstream page was
> public but then made secure, so i
I have a problem that I thought I knew how to solve but must be just having a
mind blank moment.
If the upstream server returns a 401 response I want to make sure Nginx serves
the response. Right now it is serving the stale version. What happened is that
the upstream page was public but then ma
Hello.
I've recently experimented with the `http2_push_preload` directive to
preemptively
submit a response to an XHR request. I've noticed that in the request that nginx
performs to fetch the hinted resource, no cookies are submitted. However, Chrome
does not consider the cached response a candi
12 matches
Mail list logo
