passenger 4.0.59 → 4.0.60

data/packaging/debian/debian_specs/nginx/copyright

@@ -0,0 +1,196 @@
+Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: nginx
+Source: http://nginx.org/en/download.html
+
+Files: *
+Copyright: 2002-2014 Igor Sysoev
+           2011-2014 Nginx, Inc.
+                     Maxim Dounin
+                     Valentin V. Bartenev
+License: BSD-2-clause
+
+Files: src/core/ngx_murmurhash.c
+Copyright: Copyright (C) Austin Appleby
+License: BSD-2-clause
+
+Files: src/core/ngx_proxy_protocol.h
+       src/core/ngx_proxy_protocol.c
+Copyright: Copyright (C) Roman Arutyunyan
+           Copyright (C) Nginx, Inc.
+License: BSD-2-clause
+
+Files: src/http/modules/ngx_http_scgi_module.c
+       src/http/modules/ngx_http_uwsgi_module.c
+Copyright: Copyright (C) Igor Sysoev
+           Copyright (C) Nginx, Inc.
+           Copyright (C) Manlio Perillo (manlio.perillo@gmail.com)
+License: BSD-2-clause
+
+Files: contrib/geo2nginx.pl
+Copyright: 2005, Andrei Nigmatulin
+License: BSD-2-clause
+
+Files: debian/modules/headers-more-nginx-module/*
+Copyright: Copyright (c) 2009-2014, Yichun "agentzh" Zhang (章亦春) <agentzh@gmail.com>, CloudFlare Inc.
+           Copyright (c) 2010-2013, Bernd Dorn
+           Copyright (c) Igor Sysoev
+License: BSD-2-clause
+
+Files: debian/modules/nginx-development-kit/*
+Copyright: Marcus Clyne
+License: BSD-3-clause
+
+Files: debian/modules/nginx-development-kit/src/hash/md5.h
+       debian/modules/nginx-development-kit/src/hash/sha.h
+Copyright: Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
+License: BSD-4-clause
+
+Files: debian/modules/nginx-auth-pam/*
+Copyright: 2008-2013, Sergio Talens Oliag
+License: BSD-2-clause
+
+Files: debian/modules/nginx-echo/*
+Copyright: Copyright (c) 2009-2014, Yichun "agentzh" Zhang <agentzh@gmail.com>
+License: BSD-2-clause
+
+Files: debian/modules/nginx-lua/*
+Copyright: Copyright (C) 2009-2014, by Xiaozhe Wang (chaoslawful) <chaoslawful@gmail.com>.
+           Copyright (C) 2009-2014, by Yichun "agentzh" Zhang (章亦春) <agentzh@gmail.com>, CloudFlare Inc.
+License: BSD-2-clause
+
+Files: debian/modules/nginx-upstream-fair/*
+Copyright: Copyright (c) 2007 Grzegorz Nosek
+           Igor Sysoev
+License: BSD-2-clause
+
+Files: debian/modules/nginx-http-push/*
+Copyright: Copyright (c) 2009 Leo Ponomarev
+License: Expat
+
+Files: debian/modules/nginx-upload-progress/*
+Copyright: Brice Figureau
+           2002-2007, Igor Sysoev
+License: BSD-2-clause
+
+Files: debian/modules/nginx-cache-purge/*
+Copyright: 2009-2012, FRiCKLE <info@frickle.com>,
+           2009-2012, Piotr Sikora <piotr.sikora@frickle.com>
+License: BSD-2-clause
+
+Files: debian/modules/nginx-dav-ext-module/*
+Copyright: Arutyunyan Roman <arut@qip.ru>
+License: BSD-2-clause
+
+Files: debian/modules/ngx-fancyindex/*
+Copyright: Copyright (c) Adrian Perez <aperez@igalia.com>
+License: BSD-2-clause
+
+Files: debian/modules/ngx_http_substitutions_filter_module/*
+Copyright: Copyright (C) 2014 by Weibin Yao <yaoweibin@gmail.com>
+License: BSD-2-clause
+
+Files: debian/*
+Copyright: 2007-2009, Fabio Tranchitella <kobold@debian.org>
+           2008,      Jose Parrella <joseparrella@cantv.net>
+           2009-2014, Kartik Mistry <kartik@debian.org>
+           2010-2014, Michael Lustfield <michael@lustfield.net>
+           2011       Dmitry E. Oboukhov <unera@debian.org>
+           2011-2013, Cyril Lavier <cyril.lavier@davromaniak.eu>
+           2013-2014, Christos Trochalakis <yatiohi@ideopolis.gr>
+License: BSD-2-clause
+
+License: BSD-2-clause
+ All rights reserved.
+ .
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions are
+ met:
+ .
+ 1. Redistributions of source code must retain the above copyright
+    notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+    notice, this list of conditions and the following disclaimer in the
+    documentation and/or other materials provided with the distribution.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
+ IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
+ TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+ PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+ OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+ LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+ DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+ OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+License: BSD-3-clause
+ All rights reserved.
+ .
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions are
+ met:
+ 1. Redistributions of source code must retain the above copyright
+    notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+    notice, this list of conditions and the following disclaimer in the
+    documentation and/or other materials provided with the distribution.
+ 3. Neither the name of the University nor the names of its contributors
+    may be used to endorse or promote products derived from this
+    software without specific prior written permission.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+ PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS
+ BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+ CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+ SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
+ BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
+ WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
+ OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
+ ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+License: BSD-4-clause
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the above copyright
+    notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+    notice, this list of conditions and the following disclaimer in the
+    documentation and/or other materials provided with the distribution.
+ 4. Neither the name of the University nor the names of its contributors
+    may be used to endorse or promote products derived from this software
+    without specific prior written permission.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+ FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ SUCH DAMAGE.
+
+License: Expat
+ Permission is hereby granted, free of charge, to any person obtaining a copy
+ of this software and associated documentation files (the "Software"), to
+ deal in the Software without restriction, including without limitation the
+ rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
+ sell copies of the Software, and to permit persons to whom the Software is
+ furnished to do so, subject to the following conditions:
+ .
+ The above copyright notice and this permission notice shall be included in
+ all copies or substantial portions of the Software.
+ .
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
+ IN THE SOFTWARE.

data/packaging/debian/debian_specs/nginx/debian-full.lintian-overrides

@@ -0,0 +1 @@
+nginx-full: spelling-error-in-binary usr/sbin/nginx tEH the

data/packaging/debian/debian_specs/nginx/gbp.conf

@@ -0,0 +1,2 @@
+[DEFAULT]
+pristine-tar = True

data/packaging/debian/debian_specs/nginx/help/docs/fcgiwrap

@@ -0,0 +1,14 @@
+##
+#  File:
+#    fcgiwrap
+#  Description:
+#    The fcgiwrap tool allows a user to quickly and painlessly setup a socket
+#    to handle CGI requests. This is useful for Python, Perl, etc.
+##
+
+The easy way:
+apt-get install fcgiwrap
+
+The less-easy way:
+If your distribution does not provide it, the Nginx wiki describes the steps.
+http://wiki.nginx.org/Fcgiwrap

data/packaging/debian/debian_specs/nginx/help/docs/php

@@ -0,0 +1,119 @@
+##
+#  File:
+#    php
+#  Description:
+#    This file is meant to help users get a basic understanding of a PHP stack
+#    with Nginx as the web server.
+##
+
+# Note: This is not a configuration sample and comment lines will be userd differently.
+
+
+== PHP Options ==
+
+There are a number of options that can be used to provide PHP. The two most
+common methods are php-cgi and php-fpm. The php-fpm option is relatively new
+and is not yet a standard option. This package is stable however and is moving
+toward being a standard option in distribution repositories.
+
+== PHP-FPM ==
+
+The php-fpm option is considerably harder to debug. However, the hardest issues
+to debug should be solved by including that fastcgi_params file provided by
+this package. It should at a minimum remove all silent errors.
+
+# sudo apt-get install php5-fpm
+
+If you do not have php5-fpm available, you will want to add the repository for
+the package.  https://launchpad.net/~nginx/+archive/php5
+
+In php5-fpm, you will want to edit the php pool.
+Edit /etc/php5/fpm/pool.d/www.conf
+
+The listen directive is the most important piece in this file. It is suggested
+to listen to a local unix socket. This listen directive will be used in your
+nginx configuration.
+Example: listen = /tmp/phpfpm.socket
+
+The rest of this file can be tweaked to your liking.
+
+== PHP-CGI ==
+
+The simplest and easiest method to run PHP is to use php-cgi. It does not offer
+the ability to monitor and restart processes that hang or die however.
+
+# sudo apt-get install php5-cgi
+
+To make php5-cgio work, you will need to create an init script.
+
+===== FILE: /etc/init.d/phpcgi =====
+#!/bin/bash
+#
+### BEGIN INIT INFO
+# Provides:          php-fcgi
+# Required-Start:    $local_fs $remote_fs $network $syslog
+# Required-Stop:     $local_fs $remote_fs $network $syslog
+# Default-Start:     2 3 4 5
+# Default-Stop:      0 1 6
+# Short-Description: starts php-cgi processes
+# Description:       starts php-cgi using start-stop-daemon for each user
+### END INIT INFO
+
+# Number of PHP processes to be able to handle connections.
+CHILD=10
+# Maximum number of requests each child should handle before being regenerated
+MAX_REQS=750
+
+start() {
+        start-stop-daemon --quiet --start --background --chuid "www-data" \
+          --exec /usr/bin/env \
+          -- - USER="www-data" \
+          PATH=/usr/bin PHP_FCGI_CHILDREN=$CHILD PHP_FCGI_MAX_REQUESTS=$MAX_REQS \
+          php-cgi -b /tmp/phpcgi.socket &
+}
+
+stop() {
+        killall -w php-cgi
+        rm /tmp/phpcgi.socket
+        sync
+        sleep 1
+}
+
+case "$1" in
+        start) start;;
+        stop) stop;;
+        restart) stop; start;;
+        *) echo "Usage: php-fastcgi {start|stop|restart} [user]"; exit 1;;
+esac
+===== END FILE =====
+
+# Make file executable
+chmod +x /etc/init.d/phpcgi
+
+# Add file to startup
+update-rc.d phpcgi defaults
+
+== Using PHP in Nginx ==
+
+In order to use the sockets you created (/tmp/phpfpm.socket or /tmp/phpcgi.socket)
+you will need to add a php block to your Nignx configuration.
+
+# This block adds a little security.
+# See /usr/share/doc/nginx/examples/drupal for context
+location ~ \..*/.*\.php$ {
+	return 403;
+}
+
+# This is basic PHP block that can be used to handle all PHP requests.
+# See /usr/share/doc/nginx/examples/drupal for context
+location ~ \.php$ {
+	fastcgi_split_path_info ^(.+\.php)(/.+)$;
+	include fastcgi_params;
+	# Intercepting errors will cause PHP errors to appear in Nginx logs
+	fastcgi_intercept_errors on;
+	fastcgi_pass unix:/tmp/phpcgi.socket;
+}
+
+# The above example will use php5-cgi which is bound to /tmp/phpcgi.socket.
+# If you choose to use php5-fpm the example above will bind to /tmp/phpcgi.socket
+# instead and this should be used for fastcgi_pass instead.

data/packaging/debian/debian_specs/nginx/help/docs/support-irc

@@ -0,0 +1,28 @@
+##
+#  File:
+#    support-irc
+#  Description:
+#    This file explains how to get support on IRC.
+##
+
+Nginx has a moderately active IRC channel on Freenode.
+
+You can get there by:
+  * Client
+    Using an IRC Client and pointing it to:
+    #nginx on irc.freenode.net
+  * Browser
+    Opening a web browser and pointing it to:
+    http://webchat.freenode.net?channels=nginx
+
+Common sense is expected to be followed:
+  * Code of Conduct
+    http://www.ubuntu.com/community/conduct
+  * IRC Etiquette
+    http://www.ircbeginner.com/ircinfo/etiquette.html
+  * Patience
+    If somebody doesn't answer you right away, then wait.
+    Even active IRC users have to run off sometimes.
+
+If you need more help with IRC The Linux Documentation Project has more information:
+  http://tldp.org/HOWTO/IRC/beginners.html

data/packaging/debian/debian_specs/nginx/help/docs/upstream

@@ -0,0 +1,51 @@
+##
+#  File:
+#    upstream
+#  Description:
+#    This file describes how to use upstream blocks.
+##
+
+An upstream block allows you to set a list of upstream locations for both
+proxy_pass and fastcgi_pass directives.
+
+Examples of upstream blocks:
+
+# PHP listening on the same server
+upstream php {
+	# ip_hash ensures the same backend is used for client reconnects.
+	ip_hash;
+	# This assumes we have multiple PHP listeners on different known ports.
+	server 127.0.0.1:9000;
+	server 127.0.0.1:9001;
+	server 127.0.0.1:9002;
+	server 127.0.0.1:9003;
+	# In addition to listening on ports, we can listen to unix sockets.
+	server unix:/tmp/php-cgi.socket;
+}
+
+# Multiple backend Apache instances on separate servers
+upstream apache {
+	# Adding a weight alters the chance the upstream server will be used.
+	server apache1.domain.com weight 5;
+	server apache2.domain.com;
+	server apache3.domain.com;
+	# Adding 'down' keeps the upstream from being used. Useful for downtime management.
+	server apache4.domain.com down;
+	server apache5.domain.com;
+}
+
+Using an upstream location:
+
+# Passing PHP to upstream
+location ~ \.php$ {
+	fastcgi_split_path_info ^(.+\.php)(/.+)$;
+	include fastcgi_params;
+	fastcgi_pass php;
+}
+
+# Passing all requests for /cgi-bin/* to Apache upstreams.
+location /cgi-bin {
+	proxy_pass apache;
+}
+
+For more information see http://wiki.nginx.org/HttpUpstreamModule

data/packaging/debian/debian_specs/nginx/help/examples/drupal

@@ -0,0 +1,114 @@
+##
+#  File:
+#    drupal
+#  Description:
+#    This file is meant to offer a very detailed set of instructions and best
+#    practices for deploying a Drupal website with Nginx. This file should be
+#    almost drop-in if the user is able to understand the three lines that
+#    need to be changed.
+##
+
+server {
+
+	# This is the URI of your website. You can specify multiple sites to be
+	# served by the same Drupal installation.
+	server_name domain.com www.domain.com .example.net;
+
+	# This is the root of the Drupal directory.
+	# Note that Drupal 6, Drupal 7, and Pressflow are interchangeable
+	root /var/www/drupal6;
+ 
+	# In some cases a favicon does not exist but this is not something you
+	# normally need to worry about. It's also a microscopic image and will
+	# just clutter the logs.
+	location = /favicon.ico {
+		log_not_found off;
+		access_log off;
+	}
+ 
+	# This is for the robots.txt file used by search engines.
+	location = /robots.txt {
+		# If you have one, you want to allow them access to it.
+		allow all;
+		# If you don't have one, you don't want to fill your logs with
+		# not found errors.
+		log_not_found off;
+		access_log off;
+	}
+ 
+	# This matters if you use drush because drush copies backups of modules
+	# to this directory. In the event personal information wound up in the
+	# module, you want to know outside users can't access it.
+	location = /backup {
+		deny all;
+	}
+
+	# Very rarely should these ever be accessed outside of your lan
+	# The above location for robots.txt is an exact match and will override
+	# this location block.
+	location ~* \.(txt|log)$ {
+		allow 192.168.0.0/16;
+		deny all;
+	}
+
+	# This location block protects against a known attack. It happens if
+	# the attacker uploads a non-php file and attempts to run it as a
+	# php file on the server.
+	location ~ \..*/.*\.php$ {
+		return 403;
+	}
+ 
+	# This is our primary location block. The try_files directive will
+	# attempt to serve the data in the order listed. First try the exact
+	# request (such as an image or text file). If it doesn't exist, see if
+	# the directory exists. If not, then we move to the rewrite which is
+	# used for the front-end controller pattern.
+	location / {
+		try_files $uri $uri/ @rewrite;
+	}
+ 
+	# This will rewrite our request from domain.com/node/1/ to domain.com/index.php?q=node/1
+	# This could be done in try_files without a rewrite however, the GlobalRedirect
+	# module enforces no slash (/) at the end of URL's. This rewrite removes that
+	# so no infinite redirect loop is reached.
+	location @rewrite {
+		rewrite ^/(.*)$ /index.php?q=$1;
+	}
+ 
+	# If a PHP file is served, this block will handle the request. This block
+	# works on the assumption you are using php-cgi listening on /tmp/phpcgi.socket.
+	# Please see the php example (usr/share/doc/nginx/exmaples/php) for more
+	# information about setting up PHP.
+	# NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini
+	location ~ \.php$ {
+		fastcgi_split_path_info ^(.+\.php)(/.+)$;
+		include fastcgi_params;
+		# Intercepting errors will cause PHP errors to appear in Nginx logs
+		fastcgi_intercept_errors on;
+		fastcgi_pass unix:/tmp/phpcgi.socket;
+	}
+ 
+	# The ImageCache module builds an image 'on the fly' which means that
+	# if it doesn't exist, it needs to be created. Nginx is king of static
+	# so there's no point in letting PHP decide if it needs to be servered
+	# from an existing file.
+	# If the image can't be served directly, it's assumed that it doesn't
+	# exist and is passed off to PHP via our previous rewrite to let PHP
+	# create and serve the image.
+	# Notice that try_files does not have $uri/ in it. This is because an
+	# image should never be a directory. So there's no point in wasting a
+	# stat to serve it that way.
+	location ~ ^/sites/.*/files/imagecache/ {
+		try_files $uri @rewrite;
+	}
+
+	# As mentioned above, Nignx is king of static. If we're serving a static
+	# file that ends with one of the following extensions, it is best to set
+	# a very high expires time. This will generate fewer requests for the
+	# file. These requests will be logged if found, but not if they don't
+	# exist.
+	location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
+		expires max;
+		log_not_found off;
+	}
+}