![]() # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000įastcgi_param SCRIPT_FILENAME /nginx$fastcgi_script_name # proxy the PHP scripts to Apache listening on 127.0.0.1:80 # redirect server error pages to the static page /50x.html # '"$http_user_agent" "$http_x_forwarded_for"' # '$status $body_bytes_sent "$http_referer" ' #log_format main '$remote_addr - $remote_user "$request" ' # imap_capabilities "IMAP4rev1" "UIDPLUS" # gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript # restricts the amount of connections from a single ip address # # Control maximum number of simultaneous connections for one session i.e. # limit_zone slimits $binary_remote_addr 5m # 1m can handle 32000 sessions with 32 bytes/session, set to 5m x 32000 session # # Directive describes the zone, in which the session states are stored i.e. # client will take nothing, then nginx is shutting down the connection. # transfer of answer, but only between two operations of reading, if after this time # Directive assigns response timeout to client. # time the client send nothing, nginx returns error "Request time out" (408). ![]() ![]() # The timeout is set only if a header is not get in one readstep. # Directive assigns timeout with reading of the title of the request of client. # this time the client send nothing, nginx returns error "Request time out" # The timeout is set only if a body is not get in one readstep. # Directive sets the read timeout for the request body from client. # this parameter, nginx does not send a Keep-Alive header (though this is not what makes a connection "keep-alive"). # convince some browsers to close the connection, so that the server does not have to. # the time value in the header Keep-Alive: timeout=time of the response. # The server will close connections after this time. # The first parameter assigns the timeout for keep-alive connections with the client. This will also help combat bad bots and DoS attacks. # if at the end of working request connection converts to state keep-alive, then these buffers are freed. # By default the size of one buffer is equal to the size of page, depending on platform this either 4K or 8K, # Directive assigns the maximum number and size of buffers for large headers to read from client request. ![]() Increase this when you are getting file uploads via the POST method. If size is greater the given one, then the client gets the error # Directive assigns the maximum accepted body size of client request, indicated by the line Content-Length # or a large cookie sent from the client (e.g., wap client). Increase this if you have a custom header # majority of requests a buffer size of 1K is sufficient. # Directive sets the headerbuffer size for the request header from client. # If the request body is more than the buffer, then the entire request body or some part is written in a temporary file. # (default is 8k or 16k) The directive specifies the client request body buffer size. # connect after the max has been reached will be denied access. # setup to handle 3*64=192 concurrent connections in total. # for the total amount of connections Nginx will handle. # (default: 1024) Note: Multiply worker_processes times worker_connections # single child process will handle by themselves at any one time. ![]() # worker_connections : This is the amount of client connections a # you may want to leave one core for the system and its interrupts # author cedric.walter, # to be saved in /etc/nginx/nf > keep it simple and script the stuff which ain'tĭo you have a complete tutorial for that setup? > want so you might have to make it yourself. > I haven't seen any GUI kind of setup for what you > file here and tell us whats not working. Drop apc and go for xcache, drop your nginx config ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |