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";
}
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
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 error that "too many redirects"
What's problem?
---
13 matches
Mail list logo
