On Tuesday 12 March 2013 01:44:01 ct2k7 wrote:
> I've compiled nginx with the SPDY patch, at the current latest, so nginx
> 1.3.14. As far as I can tell, the make was fine, no errors. I'm compiling
> against openSSL of the system: OpenSSL 1.0.1c 10 May 2012, on my CentOS 6.3
> server (OVH Kernel).
On 11 Mar 2013 03h17 CET, vb...@nginx.com wrote:
> Please, verify the patch file:
>
> % md5sum patch.spdy.txt
> a5cb5cb3fc8a8e04efb62b2f8f48a5ac patch.spdy.txt
>
> % shasum patch.spdy.txt
> 1a9ffddffbde0812b67eaca91a22ff0aa17293cc patch.spdy.txt
>
> Also, note that "patch --dry-run" (or "patch
http-only and secure are directives intended for browser. If the browser
doesn't detect HTTP proto for http-only setting and SSL for secure setting
then browser will drop the cookie and will never make it to the web server.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236394,237245#m
I've compiled nginx with the SPDY patch, at the current latest, so nginx
1.3.14. As far as I can tell, the make was fine, no errors. I'm compiling
against openSSL of the system: OpenSSL 1.0.1c 10 May 2012, on my CentOS 6.3
server (OVH Kernel). Server has ok amount of RAM, at least 20GB is free.
.
Left out the fact make file is used to create the link.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236654,237243#msg-237243
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Late to contribute as well but wanted to mention that we reference a single
include in the main config that gets linked to the actual file at the
deployment time only.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236654,237242#msg-237242
__
Hello all:
I had a few subtle question on NGINX operation and in particular are of
reseading configuration :
-- Assuming NGINX processes are running and the configuration is syntacaly
valid, what it the difference when '.../nginx -s reload' is executed versus
'kill -HUP ' is executed? Is ther any
>> After reading "nginx does not suck at ssl":
>>
>> http://matt.io/entry/ur
>>
>> I'm using:
>>
>> ssl_ciphers
>> ALL:!aNULL:!ADH:!eNULL:!MEDIUM:!LOW:!EXP:!kEDH:RC4+RSA:+HIGH;
>
> Some of us use the following to mitigate BEAST attacks:
> ssl_ciphers
> ECDHE-RSA-AES128-SHA256:AES128-GCM-SHA256:RC4
>> It looks like these changes from default are required for SSL session
>> resumption and to mitigate the BEAST SSL vulnerability:
>>
>> ssl_session_cache shared:SSL:10m;
>> ssl_ciphers RC4:HIGH:!aNULL:!MD5;
>> ssl_prefer_server_ciphers on;
>>
>> Should the defaults be changed to these?
>
> The BE
Hello!
On Sat, Mar 09, 2013 at 10:43:47PM +0800, Ji Zhang wrote:
> Hi,
>
> I'm doing some research on FastCGI recently. As I see from the FastCGI
> specification, it does support multiplexing through a single
> connection. But apparently none of the current web servers, like
> Nginx, Apache, or
Thank you very much, and sorry for the repeated question. I will dig deeper
before asking next time.
Regards,
Kiril
On Mar 11, 2013, at 1:17 PM, Maxim Dounin wrote:
> Hello!
>
> On Mon, Mar 11, 2013 at 09:58:28AM +0200, Kiril Kalchev wrote:
>
>> After I read the thread, I am wondering what i
Hello!
On Sun, Mar 10, 2013 at 02:43:11PM -0700, Grant wrote:
> >> nginx seems to require being pointed to an HTTP server for imap
> >> authentication. Here's the protocol spec:
> >>
> >> http://wiki.nginx.org/MailCoreModule#Authentication
> >>
> >> Is the idea to program this server yourself or
Hello!
On Mon, Mar 11, 2013 at 09:58:28AM +0200, Kiril Kalchev wrote:
> After I read the thread, I am wondering what is the recommended way to purge
> nginx cache?
Recommended way is to assume you can't purge the cache, much like
you can't purge caches in client's browsers and/or intermediate
Hello!
On Mon, Mar 11, 2013 at 10:20:10AM +0100, Jan Wrobel wrote:
> Hi,
>
> Currently I have auth_request module configured to return static pages
> on 401 and 403 errors. This looks like this:
>
> auth_request /auth/api/is-authorized/;
> error_page 401 /auth/login.html;
> error_page 403 /auth
Hello!
On Sun, Mar 10, 2013 at 09:48:47PM -0700, Grant wrote:
> It looks like these changes from default are required for SSL session
> resumption and to mitigate the BEAST SSL vulnerability:
>
> ssl_session_cache shared:SSL:10m;
> ssl_ciphers RC4:HIGH:!aNULL:!MD5;
> ssl_prefer_server_ciphers on
Hi All,
Is it possible to have multiple docroot for a single domain? and will load
different docroot based on condition?
our developers are currently developing our application but based on a new
framework. so they would like to be able to have the legacy framework and
the new framework to co-exi
Hi,
Currently I have auth_request module configured to return static pages
on 401 and 403 errors. This looks like this:
auth_request /auth/api/is-authorized/;
error_page 401 /auth/login.html;
error_page 403 /auth/not_authorized.html;
Instead of this, is it possible to return 401 and 403 response
On Sat, 9 Mar 2013 21:55:13 -0800, Grant wrote:
> After reading "nginx does not suck at ssl":
>
> http://matt.io/entry/ur
>
> I'm using:
>
> ssl_ciphers
> ALL:!aNULL:!ADH:!eNULL:!MEDIUM:!LOW:!EXP:!kEDH:RC4+RSA:+HIGH;
Some of us use the following to mitigate BEAST attacks:
ssl_ciphers ECDHE-RSA
Hello!
After I read the thread, I am wondering what is the recommended way to purge
nginx cache?
Regards,
Kiril
On Mar 10, 2013, at 6:30 PM, Maxim Dounin wrote:
> Hello!
>
> On Sat, Mar 09, 2013 at 07:52:40PM -0500, michael.heuberger wrote:
>
>> Hello guys
>>
>> I'm having this problem too
On Sat, Mar 09, 2013 at 04:56:56PM +1300, Steve Holdoway wrote:
> On 09/03/13 16:51, moke110007 wrote:
> > Nobody reply.
> > Tested,iphash and weight,support balance.
> > Over.
> >
> >
> Last time I used it, weight wasn't supported on iphash so I just used
> multiple entries to weight instead.
Qu
On 3/11/13 5:18 AM, António P. P. Almeida wrote:
> On 11 Mar 2013 01h58 CET, vb...@nginx.com wrote:
>
>> You're probably doing something wrong. I've just checked it myself:
>
> I just reproduced all your commands below with the same result. I.e.,
> no clean application, with rejection of some hun
21 matches
Mail list logo
