reaman Wrote:
---
> reaman Wrote:
> ---
> > I come to you because I am facing a problem with the customization
> of
> > the 401 error page in fact I use Nginx and rutorrent, I proceeded
> as
> >
Can you try
listen IP:80;
instead of
listen 80;
where IP is the IP address both domains resolve to ( and I assume its the
same IP).
--
*Anoop P Alias*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
reaman Wrote:
---
> I come to you because I am facing a problem with the customization of
> the 401 error page in fact I use Nginx and rutorrent, I proceeded as
> follows:
>
> I create a folder named "error_pages" I placed in the /var/www/
> then
I come to you because I am facing a problem with the customization of the
401 error page in fact I use Nginx and rutorrent, I proceeded as follows:
I create a folder named "error_pages" I placed in the /var/www/
then I created my pages 400.html 401.html 403.html 404.html 503.html
50x.html
I creat
Hi!
I just did a lemp setup but I can't get my virtual hosts to work properly.
I´m totally lost and out of ideas.
Two domains and one starting on e is always responding showing its root and
the other starting on s is just dead. I understand that nginx is handling
this as Apache analyzing the heade
The way I do this is to use multiple server {} blocks, and put all the
non-canonical hostnames / port 80 requests in a server block with a return
301 to the canonical (and HTTPS) host which only listens on 443 and the
canonical hostname.
On Fri, Mar 11, 2016 at 9:12 PM, mevans336
wrote:
> We cur
We currently use the following method to perform an http to https rewrite.
rewrite ^ https://$server_name$request_uri permanent;
I am planning to change it to the preferred method of:
return 301 https://$server_name$request_uri;
However, we'd like to also make sure any requests for domain.com a
Hello!
On Fri, Mar 11, 2016 at 02:40:34PM +, Phil Lello wrote:
> Hi,
>
> What's the best place to find details on planned features for HTTP/2
> support?
>
> I've only been looking at HTTP/2 for a few days, so forgive me if this is
> already covered.
>
> It seems pretty obvious to me that i
Hi Valentin,
Thanks for clearing up . I was looking at the wrong module.
Do you have any comments to the other two questions?
Frank
On Friday, March 11, 2016, Valentin V. Bartenev wrote:
> On Thursday 10 March 2016 14:55:06 Frank Liu wrote:
> > Hi,
> >
> > I saw this example at serverfault.com:
Hi,
What's the best place to find details on planned features for HTTP/2
support?
I've only been looking at HTTP/2 for a few days, so forgive me if this is
already covered.
It seems pretty obvious to me that it provides an opportunity for
potentially significant performance gains if changes are
Never mind, Nginx was actually limiting requests correctly.
What I was seeing in my logs was requests for non-existent .js and .css
files, which were then being passed to index.php as per my try_files in the
/ location block.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,265244,26524
Hello!
On Fri, Mar 11, 2016 at 11:32:13AM +0800, 18620708...@163.com wrote:
> nginx1.94 ssl use TLS1.0.
> server {
> listen 443;
> server_name a.com;
>
> ssi on;
> ssi_silent_errors on;
> ssi_types text/shtml;
>
> ssl on;
> s
I have a location ~* \.php$ with limit_req set inside it. But requests
outside of this location block, e.g. for .js and .css files are also being
limited. I only want to limit the number of requests to .php files.
This is my config:
worker_processes 2;
pid logs/nginx.pid;
events {
work
On Thursday 10 March 2016 14:55:06 Frank Liu wrote:
> Hi,
>
> I saw this example at serverfault.com:
>
> server {
> ...
> resolver 127.0.0.1;
> set $backend "http://dynamic.example.com:80";;
> proxy_pass $backend;
> ...
> }
>
> I have a few questions:
> 1) If the resolver DNS
On 3/11/16 12:47 PM, B.R. wrote:
[...]
> 3) This
> page http://nginx.org/en/docs/stream/ngx_stream_core_module.html#resolver
> says "This directive is available as part of our commercial
> subscription.". Is that still up to date? Can "resolver",
> "resolver_timeout" be used in
On Thu, Mar 10, 2016 at 11:55 PM, Frank Liu wrote:
> server {
> ...
> resolver 127.0.0.1;
> set $backend "http://dynamic.example.com:80";;
> proxy_pass $backend;
> ...
> }
>
> I have a few questions:
> 1) If the resolver DNS becomes unavailable (say connection timeout), what
>
16 matches
Mail list logo
