Your question shows you need to understand how HTTP over TLS works.
TLS enciphers HTTP content, thus nothing is readable (either headers or
body).
How do you select the right certificate based on HTTP content? You can't.
Wait, Host-HTTP-Header-based certificate delivery exists, how is that
possib
Alex Samad:
Is it possible with nginx to do this
https://www.abc.com
/
/noclientcert/
/clientcert/
so you can get to / with no client cert, but /clientcert/ you need a
cert, but for /noclientcert/ you don't need a cert.
as far as I learned it's not possible and the usual answer
to such fea
Hi
Is it possible with nginx to do this
https://www.abc.com
/
/noclientcert/
/clientcert/
so you can get to / with no client cert, but /clientcert/ you need a
cert, but for /noclientcert/ you don't need a cert.
Looks like from the config doco you can only set it for the whole tree ...
A
Hello!
On Fri, Jan 29, 2016 at 8:40 PM, Kurt Cancemi wrote:
> I was doing some debugging and though I haven't found a fix. The problem is
> in the ngx_http_echo_client_request_headers_variable() function c->buffer is
> NULL when http v2 is used for some reason (internal to nginx).
>
This is expec
You need to define a location block that points to the content you wish to
serve.
This page may be of help to you:
http://nginx.org/en/docs/beginners_guide.html
Best regards,
Kevin
--
Kevin Worthington
kworthing...@gmail.com
http://kevinworthington.com/
http://twitter.com/kworthington
On Mon, Ja
On Mon, Feb 01, 2016 at 04:24:20PM +, Radha Venkatesh (radvenka) wrote:
Hi there,
> And I issued the curl command like this, but I still see this error
>
> curl -v http://128.107.138.162:8080/rhesos-server/rhesos/api/v1/ping
>
> * About to connect() to 128.107.138.162 port 8080 (#0)
> * T
Francis,
Thank you for pointing out the discrepency in the ip address. I have fixed
that and the netstat out looks like this
netstat -anp | grep 8080
tcp0 0 128.107.138.162:80800.0.0.0:* LISTEN
And I issued the curl command like this, but I still see this erro
Hello!
On Sat, Jan 30, 2016 at 05:31:14PM +0100, Thomas Nyberg wrote:
> Hello I've set up an http proxy to a couple of other servers and am using
> max_fails and fail_time in addition to having a proxy_read_timeout to force
> failover in case of a read timeout. It seems to work fine, but I have t
Hello!
On Mon, Feb 01, 2016 at 12:24:22AM -0500, rgrraj wrote:
> Hi
>
> Thank you all for the suggestions and thoughts.
>
> I did double check the nginx version I am having and it is 1.9.2.
> root@ser2:~# nginx -V
> nginx version: nginx/1.9.2
> built by gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu
On Mon, Feb 01, 2016 at 12:24:22AM -0500, rgrraj wrote:
Hi there,
> Thank you all for the suggestions and thoughts.
>
> I did double check the nginx version I am having and it is 1.9.2.
> but when I use the expires directive it shows invalid error same as before.
>
> Seems like to get the f
On Mon, Feb 01, 2016 at 01:00:04AM +, Radha Venkatesh (radvenka) wrote:
Hi there,
> server {
> listen 127.107.138.162:8080;
> However, when I use the curl command to send a request using the proxy like
> this, I see a "Connection Refused"
>
>
> curl -v -x 'http://:@128.107.138
11 matches
Mail list logo