Choose your favorite products and items, tell your life to bring some fun,
welcome to join efox shop
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241210,241467#msg-241467
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailm
I have also a cacti graph, representing the state of tcp connections for the
period of the accident:
http://unix.zhegan.in/files/tcp_connections.png
looks like handshakes were fine, but the the exchange was stalled for each
stream.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,240568
Hello!
On Thu, Aug 01, 2013 at 06:13:00AM -0400, microwish wrote:
> Thanks, Maxim.
>
> By "Such lines in access log are caused by opening and closing a connection
> without sending any data in it", you are meaning that a client opens a
> connection and then closes the connection actively without
Hello!
On Thu, Aug 01, 2013 at 06:11:44AM -0400, Rakshith wrote:
> I ask that question because when i tried to transfer 4GB file, i get an
> error logged which says:
>
> 2013/08/01 10:02:57 [error] 50935#0: *27 client intended to send too large
> body:
> 4582367864 bytes, client: y.y.y.y, serve
I've upgraded the nginx version 1.24 to 1.4.2, but this behavior still
happens.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241447,241459#msg-241459
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi,
Currently, we use Nginx as a reverse proxy without cache. Last monday we've
rolled out a new version of PHP application which has appeared a several 502
errors.
First of all, i've applied the workaround explained in thread
http://forum.nginx.org/read.php?2,188352 . The number of 502 have fa
Thanks, Maxim.
By "Such lines in access log are caused by opening and closing a connection
without sending any data in it", you are meaning that a client opens a
connection and then closes the connection actively without sending any data,
or that a Nginx worker process accepts a connection and the
I ask that question because when i tried to transfer 4GB file, i get an
error logged which says:
2013/08/01 10:02:57 [error] 50935#0: *27 client intended to send too large
body:
4582367864 bytes, client: y.y.y.y, server: sx1, request: "PUT /core_8GB.nz
HTTP/1.1", host: "x.x.x.x"..
Posted at Ngin
Hi,
Thanks for that reply!!.. So looks like Curl is not able to pick up the
whole file for transfer..And Does Nginx has a limit on how big a file can be
PUT/GET ??
-Rakshith
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241437,241454#msg-241454
__
Hello!
On Thu, Aug 01, 2013 at 03:20:28AM -0400, Rakshith wrote:
> Hi,
>
> I wanted to know whats the maximum file size which i can transfer using a
> simple CURL PUT/GET command. I ask this because when i try to send a file
> which is >64KB, i get a HTTP/1.1 100 Continue message:
>
> File i am
Hello!
On Thu, Aug 01, 2013 at 03:10:30AM -0400, microwish wrote:
> In access_log file, huge numbers of log entries like this:
>
> 115.85.238.34 1764839163 - 0.242 [01/Aug/2013:11:02:01 +0800] "foo.bar.com"
> "-" 400 0 "-" "-" "-"
>
>
> log_format defined in http conf block:
>
> '$remote_addr
Hello, I have a trouble with nginx caching pages it shouldn't cache. I have
uwsgi_cache enabled:
uwsgi_cache_path /tmp/cache levels=1:2 keys_zone=django:1m;
location /test {
uwsgi_pass unix:/tmp/uwsgi.sock;
uwsgi_cache django;
}
nginx caches responses that have Expires header set in the f
Hey guys,
I have been using nginx in my personal life for a couple of years, recently
dropping totally apache and I must admit that this software rocks. Congrats
to all the devs for the fantastic job in the new-event-driven-world.
Secondly, at work, we are trying to use nginx as a SSL endpoint fo
more additions:
some SSL related config in Nginx config file
ssl_protocols SSLv3 TLSv1;
ssl_ciphers RC4:AES128-SHA:3DES:!EXP:!aNULL:!kEDH:!ECDH;
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241435,241441#msg-241441
___
ngi
addtions:
no corresponding logs in error_log.
Nginx version: 1.2.4
OpenSSL version: OpenSSL 1.0.1e
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241435,241439#msg-241439
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mail
Hi,
I wanted to know whats the maximum file size which i can transfer using a
simple CURL PUT/GET command. I ask this because when i try to send a file
which is >64KB, i get a HTTP/1.1 100 Continue message:
File i am trying to do a PUT:
[rakshith~]$ ls -l nginx.tar
-rw-r--r-- 1 rakshith engr 675
Hello,
My understanding is on Apache rules like follow and convert it to nginx
If anyone request anything except follow URI /file/, /install/, /design/,
/plugins/, /phpmyadmin/ then nginx will forward anything to
/index.php?do=anything
RewriteCond %{REQUEST_URI} !^/file/.*
RewriteCond %{REQUEST_
In access_log file, huge numbers of log entries like this:
115.85.238.34 1764839163 - 0.242 [01/Aug/2013:11:02:01 +0800] "foo.bar.com"
"-" 400 0 "-" "-" "-"
log_format defined in http conf block:
'$remote_addr $connection $remote_user $request_time [$time_local]
"$hostname" "$request" $status $
18 matches
Mail list logo