Hi there,
I have built nginx 1.5.6 from source, with a 3rd party module (xtoken -
http://code.google.com/p/nginx-xtoken-module/).
I have it working fine on a 32-bit Debian Squeeze system. An identical build
on a 64-bit Centos 6.4 system, with an identical configuration file results
in the error:
server {
listen 80;
server_name www.example.com;
root /var/www/mysite;
location / {
# Default location, request will fallback here if none other
location block matches
rewrite ^.*$ / permanent; # Permanent (HTTP 301) redirection to
'root' location '/'
}
lo
I have a version of this working, but I suspect my solution is not the best
one.
Please suggest any improvements I can make to my conf file. I am attempting
to do the following:
1. If any file is requested from the root, we should always serve
"index.html". No other file should be accessible, a
Thanks,
It works for me now.
The error "550 5.7.1 Client does not have permissions to send as this
sender" is because our SMTP back-end did not accept SMTP relay from NGINX.
Configure SMTP backend allow NGINX relay fix my error.
I used xclient-> on, when I try to auth login, SMTP backend return e
It's something a lot of people are bumping on.
401 HTTP covers both failed and missing authentication but isn't possible
for Nginx to differentiate those states and thus only generate an error
message on a failed (ie not empty credentials, either user or password
containing something) attempt?
Tha
2013-10-15 Piotr Sikora
has cited Julien Vehent :
>
> ssl_ciphers
> 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDH
Thanks a ton for you!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,243869,243875#msg-243875
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Sun, Oct 20, 2013 at 04:17:34PM -0400, dalmolin wrote:
> I have set up an Nginx as a front end to manage secure connection and
> authorization for the Radicale calendar server which I use to synch my
> Lightning calendar on my desktop, laptop and Android phone (it uses the
> Caldav Sync
On Sun, Oct 20, 2013 at 04:17:34PM -0400, dalmolin wrote:
Hi there,
> One strange thing I have noticed is that I keep getting an
> error in the Nginx error log for the Android device, here are the
> abbreviated logs from Nginx's access.log and error.log:
>
> access.log entries:
> 199.7.156.144 -
On Sun, Oct 20, 2013 at 03:11:04PM -0400, agriz wrote:
> after adding error_page 404 /404.php
>
> it works for other files which are not php. It calls the error page.
> But if it is a php file, it shows "File not found."
http://nginx.org/r/fastcgi_intercept_errors
f
--
Francis Daly
I have set up an Nginx as a front end to manage secure connection and
authorization for the Radicale calendar server which I use to synch my
Lightning calendar on my desktop, laptop and Android phone (it uses the
Caldav Synch app). It all works fine after a long and steep learning curve
for me at l
server_name .site.com;
root /var/www/site.com;
error_page 404 /404.php;
access_log /var/log/nginx/site.access.log;
index index.html index.php;
if ($http_host != "www.site.com") {
rewrite ^ http://www.site.com$request_uri permanent;
}
location ~* \.php$ {
# try_files $uri
Somewhere something happened.
I am not able to fix it.
error_page 404 404.html
During the test, i had this line in the site.conf file.
404.html had "File not found."
Later i created a proper error page and changed the commands like this.
error_page 404 404.php
But nginx is still throwing "File
Richard Kearsley Wrote:
---
> On 20/10/13 11:00, talkingnews wrote:
> I'm not sure if there's a way within APT to see the version before
> installing it, but if you look directly in the 'Packages' file it says
> :
>
> Package: nginx
> Version: 1
On 20/10/13 11:00, talkingnews wrote:
It says to replace "raring" (or whatever) with the latest release.
But if I look at http://nginx.org/packages/ubuntu/dists/ I see that only
raring is the latest.
So, how can I best ensure that I can apt-get update nginx without having to
completely remove
I seem to be "stuck" on the 5 month old nginx 1.4.1 on my Ubuntu 13.04. But
reading the 13.10 (Saucy Salamander) Ubuntu repo notes, I see it's STILL
that version.
So I found this post:
http://www.devcu.com/forums/topic/633-upgrade-nginx-to-latest-stable-release-ubuntu-1204/
It says to replace "ra
16 matches
Mail list logo
