SOLVED: Re: stripping www and forcing ssl

On Fri, Mar 20, 2015 at 08:57:10PM +0200, Gena Makhomed wrote: > > Probably "include ssl_common;" contains "ssl on;" > directive, which forces nginx to use HTTPS on 50.250.218.168:80 > Yup. This was right. I was shocked because I had thought I had omitted this directive. But I looked and there it

Nginx mail proxy

I want to use nginx as a mail proxy.I am new to nginx and need some help with the configuration, I got some problems. I want to use Foxmail ,use ngx proxy , this is my configuration. mail{ #server_namemailProxy; auth_http localhost:80/php/auth.php; pop3_capa

Latest nginx debug version

Hi, I installed nginx-full-dbg on the latest Ubuntu 14.10 and after some tinkering I could add the Dynatrace Agent. While I got nginx 1.6.2 on Ubuntu I tried the same on a Fedora 18 and I end up with 1.2.9. Also: I saw some mention of a debug switch in the help, but I guess this has nothing to do

what does fastcgi_keep_conn do?

Hi, I would like nginx to serve all requests of a given TCP connection to the same FCGI server. If a new TCP connection is established, then nginx would select the next UDS FCGI server in round-robin fashion. Can this be achieved with NGINX, and if yes, how? I thought turning on fastcgi_keep_conn

Re: enable memcache with nginx

On 20.03.2015 21:36, Mohammad Tokallo wrote: i have tried to configure memcache with nginx but still couldn't configure it anybody have experience to configure memcache with nginx please send your configuration file You can find example configuration in module documentation: http://nginx.org/e

enable memcache with nginx

Dear Friends i have tried to configure memcache with nginx but still couldn't configure it anybody have experience to configure memcache with nginx please send your configuration file thanks in advance ___ nginx mailing list nginx@nginx.org http://mailma

Re: stripping www and forcing ssl

On 20.03.2015 20:35, B.R. wrote: You have a duplicate listen directive with same IP address and same port in both server blocks. I doubt that is a valid configuration. Yes, this is valid configuration. See http://nginx.org/en/docs/http/request_processing.html http://nginx.org/en/docs/http/ser

Re: stripping www and forcing ssl

On 20.03.2015 20:01, David Benfell wrote: I am attempting to strip www. and force SSL. Here are the blocks I'm using: server { listen 50.250.218.168:80; listen 50.250.218.168:443 ssl; listen [2001:470:67:2b5::10]:80; l

Default value of gzip_proxied

I recently bumped into some trouble with a client caching uncompressed data without understanding where it came from. After long investigation on what appeared to be random, I narrowed it to the gzip_proxied directive. Return c

Re: stripping www and forcing ssl

You have a duplicate listen directive with same IP address and same port in both server blocks. I doubt that is a valid configuration. Have you checked nginx -t and error logs on reload/start? I suggest you have a server block listening for HTTP on port 80 and another block reponsible for HTTPS tr

Re: Intermittent SSL Handshake Errors

I had to start looking at this issue again now that yet another openssl security issue. Now that I know I can go back to a working setup just by downgrading SSL, I am able to gather more information. This morning, I updated the libssl libraries and restarted nginx, and the errors started flooding

stripping www and forcing ssl

Hi all, I am attempting to strip www. and force SSL. Here are the blocks I'm using: server { listen 50.250.218.168:80; listen 50.250.218.168:443 ssl; listen [2001:470:67:2b5::10]:80; listen [2001:470:67:2b5::10]:443 ssl;

Re: Intermittent SSL Handshake Errors

I am seeing similar error as well. It is showing up for lot of people and am not sure why it is happening and if actually the clients facing the error are actually able to browse through the website or not. Can someone please help me understanding that is it safe to downgrade to the earlier version

Re: https to http error "too many redirects"

On 20.03.2015 13:13, Daniël Mostertman wrote: You'll _never_ reach http request since you set HSTS configuration :) If you still want some http request on your web server, disable your HSTS directive. (see Daniel statement on previous email). 1. HSTS enabled only on domain name www.example.com

Re: https to http error "too many redirects"

Gena Makhomed schreef op 20-3-2015 om 12:05: On 20.03.2015 12:36, Dewangga Bachrul Alam wrote: You'll _never_ reach http request since you set HSTS configuration :) If you still want some http request on your web server, disable your HSTS directive. (see Daniel statement on previous email). 1

Re: https to http error "too many redirects"

On 20.03.2015 12:36, Dewangga Bachrul Alam wrote: You'll _never_ reach http request since you set HSTS configuration :) If you still want some http request on your web server, disable your HSTS directive. (see Daniel statement on previous email). 1. HSTS enabled only on domain name www.example

Re: https to http error "too many redirects"

Hi! You'll _never_ reach http request since you set HSTS configuration :) If you still want some http request on your web server, disable your HSTS directive. (see Daniel statement on previous email). On 03/20/2015 05:14 PM, Gena Makhomed wrote: > On 20.03.2015 11:35, Daniël Mostertman wrote: >

Re: https to http error "too many redirects"

On 20.03.2015 11:35, Daniël Mostertman wrote: You said that in your configuration, you have the following line: # HSTS (ngx_http_headers_module is required) (15768000 seconds = 6 months) add_header Strict-Transport-Security max-age=15768000; This makes nginx send a HSTS header to browsers that

Re: https to http error "too many redirects"

You said that in your configuration, you have the following line: # HSTS (ngx_http_headers_module is required) (15768000 seconds = 6 months) add_header Strict-Transport-Security max-age=15768000; This makes nginx send a HSTS header to browsers that visit the website. With this, you tell the bro

Re: https to http error "too many redirects"

You should set it to 1 for a while and then disable it. What's mean? How can i do? Please teach me. Thanks Posted at Nginx Forum: http://forum.nginx.org/read.php?2,257458,257472#msg-257472 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.

Re: nginx fails to start - nginx.service not found

Hello, On 20/03/2015 01:08, tunist wrote: > i just built the latest mainline nginx from source on fedora 21 (64bit) and > when i run: service nginx start > > i see: > > Redirecting to /bin/systemctl start nginx.service > Failed to start nginx.service: Unit nginx.service failed to load: No such

Re: https to http error "too many redirects"

Correct, you give the HSTS header on the SSL/TLS port. So if *any* connection in the past has gone to the SSL/TLS port, the browser is forced to use https:// for any future connection. You should set it to 1 for a while and then disable it. On Mar 20, 2015 9:48 AM, "jinwon42" wrote: > Sorry. > >

Re: https to http error "too many redirects"

Sorry. 80 port is right. if ($scheme != $example_org_preferred_proto) { return 301 $example_org_preferred_proto://$server_name$request_uri; } Still saw error. "ERR_TOO_MANY_REDIRECTS" --- map $reques

Re: https to http error "too many redirects"

Why 88? 20.03.15 11:08, jinwon42 пишет: return 301 $example_org_preferred_proto://$server_name:88$request_uri; -- br, Dmitry Pryadko ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: https to http error "too many redirects"

Thanks for reply! But, I still saw error. 400 Bad Request The plain HTTP request was sent to HTTPS port this setting is wrong? map $request_uri $example_org_preferred_proto { default "https"; ~^/mobile/PayOnlyResult.do "http"; ~^/kor/companyBrand.do "http"; }

Re: https to http error "too many redirects"

You can merge both servers into one and try something like this: map $request_uri $example_org_preferred_proto { default "https"; /companyBrand.do "http"; } server { listen 80; listen 443 ssl; if ($scheme != $example_org_preferred_proto) { return 301 $example_org_prefer