So while this worked well for port 80:
On 8/20/2015 3:55 PM, Igal @ Lucee.org wrote:
> Thank you, Francis.
>> For each "listen" directive with a unique ip:port, add one server{}
>> block which contains "listen ip:port default_server; return 444;"
> This seems to do the trick.
when I tried to add
Doing a curl -I -L http://www.site1.com/ returns this:
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Fri, 21 Aug 2015 03:04:50 GMT
Content-Type: text/html
Content-Length: 178
Connection: keep-alive
Location: https://site1.com/
HTTP/1.1 200 OK
Server: nginx
Date: Fri, 21 Aug 2015 03:04:50 GMT
Note that I upgraded the server so I could turn httpv2 on.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,261156,261157#msg-261157
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
This problem may have been around before I updated to nginx version 1.9.4
but I'm not sure.
I have one VPS with two IP addresses. Server 1 redirects port 80 www and
non-www to port 443 requests along with www requests on port 443 to the
non-www web site. iow, http://(www.)site1.com/ and https://w
Thank you, Francis.
> For each "listen" directive with a unique ip:port, add one server{}
> block which contains "listen ip:port default_server; return 444;"
This seems to do the trick.
I expected there to be a way to do all of the IP addresses at once.
Thanks for your help!
Igal
On 8/20/201
On Thu, Aug 20, 2015 at 02:46:57PM -0700, Igal @ Lucee.org wrote:
> I want to disable processing of all requests that do not have a valid
> hostname
Check your entire configuration for "listen" directives.
http://nginx.org/r/listen
There will be zero or more in each server{} block. If there are
Hello,
large_client_header_buffers does not seem to work in server context,
however it works fine in http context. Documentation says it should work
for both [1] and looking at the application code it seems like it should
too [2].
I am running multiple server definitions and I've tried nginx vers
I want to disable processing of all requests that do not have a valid
hostname
I'm tried to follow the advice on:
http://nginx.org/en/docs/http/request_processing.html#how_to_prevent_undefined_server_names
so I have (inside http directive):
server {
listen 80;
server_na
Hey Guys,
We have been testing Nginx 1.8.x, and We realize that the cache
structure for Nginx 1.8.x is not compatible for Nginx 1.6.x. In other words,
by updating Nginx 1.6.x to 1.8.x, all the cache objects will be
revalidated.
We are working in a tool to migrate 1.6.x cache objects to 1.8
Hi,
first, the setup: I have 2 identical maschines running latest CentOS 6.6
and uWSGI 2.0.10, both machines had nginx-1.4.7-1.el6.ngx.x86_64
installed. I saw almost identical values for $request_time in the Nginx
log files of both machines.
We are using Nginx to serve some static files and pass
The aim of this course is to make you understand the financial statement
of a company doing an analysis on the same and projecting the future
financials of a company.The tutorials have been designed in such a
manner that it would help you build a step-by-step advanced financial
model‚ Concept of ci
Looks like it isn't just nginx (or even more likely IS an openssl issue)
because I just encountered it again with pjproject:
*
../src/pj/ssl_sock_ossl.c:1001:5: warning: implicit declaration of function
‘M_ASN1_STRING_length’ [-Wimplicit-function-declaration]
len = M_ASN1_STRING_length(X50
12 matches
Mail list logo
