On Dec 19, 2013, at 6:41 PM, "justin" wrote:
> Any update or eta on when we can expect spdy protocol version 3 in the 1.5.X
> branch?
Pretty soon, stay tuned and thanks for the patience!
> Thanks.
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,245732,245732#msg-245732
>
> ___
Hi,
On Dec 3, 2013, at 1:45 AM, Shankar Dagadu Borate wrote:
> Hi all,
>
> We are using nginx as proxy server in all our production deployment. The
> nginx server proxy the http request to Amazon ELB (elastic load balancer)
> using upstream module. Currently we are seeing timeout issues in NG
On Oct 22, 2013, at 11:37 AM, Darren Pilgrim
wrote:
> On 10/19/2013 5:07 PM, Darren Pilgrim wrote:
>> On 10/14/2013 9:37 AM, Andrew Alexeev wrote:
>>> http://barry.wordpress.com/2012/06/16/nginx-spdy-and-automattic/
>>
>> How much capital would you need to
On Oct 14, 2013, at 8:01 PM, codemonkey wrote:
> Contemplating switching my site over to Jetty to take advantage of spdy/3
> and push, but would rather stay with nginx really...
>
> Is there a "rough" ETA on spdy3 in nginx? 1 month? 6 months? 2 years?
>
> Thanks, sorry if this is a frequent
On Sep 27, 2013, at 7:09 PM, Thijs Koerselman wrote:
> Hi,
>
> I posted this on stackoverflow already but I thought I might have more luck
> here :)
>
> http://stackoverflow.com/questions/19023777/how-to-make-proxy-revalidate-resource-from-origin
>
> In short, I can't find a way to make nginx
On Sep 10, 2013, at 11:25 PM, itpp2012 wrote:
> 10:27 10-9-2013: B02 build
>
> Based on nginx 1.4.2 with;
> pcre-8.32
> zlib-1.2.8
> openssl-1.0.1e
> + Compiled with: FD_SETSIZE = 16384 (original Windows source files
> modified)
> + Now capable to handle C250K ! (with optimization registry fi
On Jul 25, 2013, at 2:49 AM, John Watson wrote:
> Upgraded from 1.2.9 to 1.4.1 and now started getting:
>
> [emerg] could not build the variables_hash, you should increase either
> variables_hash_max_size: 512 or variables_hash_bucket_size: 64
>
> Same configuration and even dropped (2) 3rd
On Jul 4, 2013, at 4:57 AM, "badtzhou" wrote:
> We have several hundred Gs of file cached using nginx. Every time we
> restarted nginx, the cache loader process will appear and server load will
> go super high and respond very slowly.
>
> Looks like cache loader process is very I/O intensive and
Hi JackB,
On May 22, 2013, at 1:38 PM, JackB wrote:
> Hello,
>
> on your Site (http://nginx.com/products.html) you are comparing NGINX SE
> with the Open Source version. The table states "Basic" and "Enhanced" on
> many core features of NGINX. The SE/"Enhanced" column offers additional
> inform
On Apr 26, 2013, at 4:12 PM, Lukas Tribus wrote:
> Hi!
>
>> Cfr. http://www.securityfocus.com/archive/1/526439/30/0/threaded
>>
>> Is 1.4.x release affected?
>
> I guess. Please see the "recent nginx security issue announce" thread.
We are still investigating. So far we can't confirm it's a f
On Apr 18, 2013, at 12:37 PM, "HajoLOcke" wrote:
> Hello,
>
> i use nginx 1.0.12 and 1.2.4
> I know there is a special healthcheckmodule. But i want to know if nginx ist
> doing a kind of healtcheck in its basic Configuration without the special
> HttpHealthcheckModule. Is nginx able to check an
Hi Dave,
On Apr 12, 2013, at 2:34 PM, ix8675...@sent.at wrote:
> Hi,
>
> I just started with a small company that's got a bunch of web apps being
> served up from a bunch of different web servers. Some are 'appliances',
> most are Apache.
>
> It's a mess of an infrastrucutre -- slow and . My
On Mar 28, 2013, at 3:57 PM, Lukas Tribus wrote:
>> Why would you doubt that? Of course, my machines may be bigger than the
>> norm...
>
> Because nginx doesn't do tcp splicing. Is my assumption wrong; are you able to
> forward 20Gbps with nginx? Then yes, probably you have huge hardware, which
Jay,
On Mar 16, 2013, at 12:37 PM, Jay Oster wrote:
> Hi Maxim,
>
> Thanks for the suggestion! It looks like packet drop is the culprit here. The
> initial SYN packet doesn't receive a corresponding SYN-ACK from the upstream
> servers, so after a 1-second timeout (TCP Retransmission TimeOut),
On Mar 3, 2013, at 10:58 AM, 张沈鹏 wrote:
> I write this and it success proxyed , but I want to let the proxy use SPDY
> there is no how to use SPDY in revese proxy in the document
There's not SPDY for upstream servers in nginx at this time, so you can't.
> server{
> listen 443;
> se
On Feb 18, 2013, at 4:03 PM, perone wrote:
> Is there any updates on the Websocket proxy support ? Everything I found is
> only this: http://trac.nginx.org/nginx/milestone/1.3.13
Yes, there will be an update very soon. Be patient and stay tuned!
___
ng
16 matches
Mail list logo
