server {
listen 80;
listen [::]:80;
return 301 https://$host$request_uri;
ssl_certificate /etc/ssl/certs/bluegrasscounty/certificate.crt;
ssl_certificate_key /etc/ssl/certs/bluegrasscounty/private.key;
server_name *.bluegrasscounty.com www.bluegrasscounty.com
bluegrasscounty.com;
Thank you Francis Daly. It works.
On 15 Sep 2017 5:45 am, "Francis Daly" wrote:
On Thu, Sep 14, 2017 at 11:54:23PM +0800, tseveendorj wrote:
Hi there,
> location / {
> index index.html;
> if ($geoip_country_code != "JP") { return 301
> https://example.co
On Thu, Sep 14, 2017 at 11:54:23PM +0800, tseveendorj wrote:
Hi there,
> location / {
> index index.html;
> if ($geoip_country_code != "JP") { return 301
> https://example.com/en/; }
> }
> location = /en/ {
Change that to "location /en/ {"
Hi,
I configured http (www, non-www) to https (non-www) and https (www) to
https (non-www). It is working fine. But I need to add geoip redirection
in location / but I got Too many redirect.
This server is behind load balancer. LB is redirecting 80 to 81 and 443
to 80.
server {
liste
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
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
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
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:
>
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
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
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.
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.
>
>
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
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
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";
}
to) {
return 301 $example_org_preferred_proto://$server_name$request_uri;
}
}
20.03.15 5:29, jinwon42 пишет:
Hi.
i have a setting problem.
I want all request "http" --> "https"
But, some location is "https" --> "http".
ALL Location : https
/companyB
Hi.
i have a setting problem.
I want all request "http" --> "https"
But, some location is "https" --> "http".
ALL Location : https
/companyBrand.do : http only
i saw e
Hi guys,
if ($scheme = "http") {
return 301 https://$server_name$request_uri;
}
Did the job indeed !
Thanks again all for your time and patience !
All the best !
2014-11-21 20:29 GMT+01:00 Francis Daly :
> On Fri, Nov 21, 2014 at 09:02:01AM +0100, JACK LINKERS wrote:
>
> Hi there,
>
>
On Fri, Nov 21, 2014 at 09:02:01AM +0100, JACK LINKERS wrote:
Hi there,
> As you can see, the template doesn't make separate server blocks for each
> HTTP & HTTPS protocole :
This part is still true:
> > What you probably want is:
> >
> > listen on http; redirect everything to https.
> > list
Hi guys,
This is not the first time I use this mailing list for support and it has
always been very helpful.
I might have forget to tell I'm using ISPConfig to setup my vhosts
The .conf file is automaticaly generated, I only add some tuning to make
different things work such as WordPress, PrestaS
On Thu, Nov 20, 2014 at 10:07:22PM +0100, JACK LINKERS wrote:
You probably already have the answer now, but just in case not...
> I completely lost...
> I tried everything (of my understanding) with no success.
Your original config was:
listen on http and https; redirect everything to https.
Here's a basic example of one of my configs that redirect example.wp.com
to https://www.example.wp.com... update and example.wp.com as
necessary, and ensure the site is set up as www.example.wp.com as well.
It may need the odd tweak to restore to standard use of fastcgi
includes, as I've modifie
Maybe start over your configuration, one step at a time, checking
everything you do has the desirect effect?
Step by step, gently, no pressure. That is the way you learn! Do not give
up, if you need specific help people are here to help you :o)
As you just realized, copy-pasting 'magic' configurat
I completely lost...
I tried everything (of my understanding) with no success.
I didn't know you could include a condition with if and came across sites
like :
http://publications.jbfavre.org/web/nginx-vhosts-automatiques-avec-SSL-et-authentification.fr
This is way beyond my skills... I didn't mana
Hi guys,
Thanks for your fast reply and input.
I didn't think of wordpress at all.
I'll try some tuning and keep you posted.
Thanks again
Le 20 nov. 2014 09:52, "B.R." a écrit :
> On Thursday, November 20, 2014, JACK LINKERS
>> wrote:
>>
>>> rewrite ^ https://$server_name$request_uri? p
>
> On Thursday, November 20, 2014, JACK LINKERS
> wrote:
>
>> rewrite ^ https://$server_name$request_uri? permanent;
>>
>
This looks highly suscpicious to me: unconditional rewrite of any request?
Try to either:
- match the regex against HTTP requests
- enclose a 'return 301 [...]' in an
It's looks like wordpress problem. Not your conf. Did you figure it out the
problem if set your wordpress into https mode?
On Thursday, November 20, 2014, JACK LINKERS wrote:
> Hello,
>
> I try to force SSL redirect on my website, but I'm getting a
> ERR_TOO_MANY_REDIRECTS.
>
> I can't figure wh
Hello,
I try to force SSL redirect on my website, but I'm getting a
ERR_TOO_MANY_REDIRECTS.
I can't figure what's wrong, here is my vhost .conf file :
server {
listen *:80;
listen *:443 ssl;
ssl on;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_certificate /var/www/clients/client2/web1/ssl/d
gt; good reason for nginx to have any part of this
>
> Sent from my iPhone
>
> On Mar 21, 2013, at 6:49 PM, "toddlahman" wrote:
>
>> The reply I received from NetDNA after supplying the same information as I
>> did here is as follows:
>>
>>
On Thu, Mar 21, 2013 at 06:48:43PM -0400, toddlahman wrote:
Hi there,
> The reply I received from NetDNA after supplying the same information as I
> did here is as follows:
>
> "Too many redirects" is a legit message in this scenario - example: You are
> redirecti
o have any part of this
Sent from my iPhone
On Mar 21, 2013, at 6:49 PM, "toddlahman" wrote:
> The reply I received from NetDNA after supplying the same information as I
> did here is as follows:
>
> "Too many redirects" is a legit message in this scenario -
The reply I received from NetDNA after supplying the same information as I
did here is as follows:
"Too many redirects" is a legit message in this scenario - example: You are
redirecting domain.com/file.jpg TO cdn.domain.com/file.jpg ---> request
comes to CDN and CDN neds to cache t
On 21 March 2013 19:39, toddlahman wrote:
> As I already said, the code doesn't work with NetDNA, so there is nothing to
> fix. A different approach must be taken, and I am looking for solutions
> other than that which is already broken.
You haven't explained *why* it's broken, or what you've don
As I already said, the code doesn't work with NetDNA, so there is nothing to
fix. A different approach must be taken, and I am looking for solutions
other than that which is already broken.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,237609,237655#msg-237655
On Thu, Mar 21, 2013 at 03:13:43PM -0400, toddlahman wrote:
Hi there,
> I talked to NetDNA and they said my redirect would in fact cause a redirect
> loop. Unfortunately the PHP project I am using the CDN for would take a long
> time to convert URLs to the CDN for static files so another route ma
On 21 March 2013 19:13, toddlahman wrote:
> I talked to NetDNA and they said my redirect would in fact cause a redirect
> loop. Unfortunately the PHP project I am using the CDN for would take a long
> time to convert URLs to the CDN for static files so another route may be a
> better solution.
>
>
I talked to NetDNA and they said my redirect would in fact cause a redirect
loop. Unfortunately the PHP project I am using the CDN for would take a long
time to convert URLs to the CDN for static files so another route may be a
better solution.
There has been mention of using proxy_pass to an upst
e to care.
If your server is configured to cause a redirect loop, it's your
problem. If their one is, it's their problem.
So: which server is causing the "Too Many Redirects"?
curl -i http://yourserver/XXico
Do you get a http redirect? What happens when you "curl -i"
to a CDN (content
> delivery network), but both ways result in the message "too many redirects."
> Can anyone tell me what I am doing wrong here?
>
> location ~* ^.+.(jpe?g|gif|css|png|js|ico)$ {
>rewrite ^ http://cdn.mydomain.com$request_uri? permanent;
>
It is possible my CDN is using the same ruleset. I am using MaxCDN, and they
use Nginx to serve static images. How would I write this ruleset to be
compatible with MaxCDN (aka NetDNA)?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,237609,237612#msg-237612
_
On Wed, 2013-03-20 at 22:47 -0400, toddlahman wrote:
> I have tried both ways to redirect my static files to a CDN (content
> delivery network), but both ways result in the message "too many redirects."
> Can anyone tell me what I am doing wrong here?
>
> location ~* ^.+.
I have tried both ways to redirect my static files to a CDN (content
delivery network), but both ways result in the message "too many redirects."
Can anyone tell me what I am doing wrong here?
location ~* ^.+.(jpe?g|gif|css|png|js|ico)$ {
rewrite ^ http://cdn.mydomain.com$r
42 matches
Mail list logo
