summaryrefslogtreecommitdiffstats
path: root/usr.sbin/nginx/src (follow)
Commit message (Collapse)AuthorAgeFilesLines
* update to 1.2.1robert2012-06-1324-430/+579
|
* move the chroot path stripping into a different function to make surerobert2012-05-151-4/+4
| | | | | that we always include aliases as well, to make "user directories work" tested by jasper@ and sthen@
* backport changeset 4619 from nginx trunk:robert2012-05-132-6/+46
| | | | | | | | | | | | Accept moderation in case of EMFILE/ENFILE. In case of EMFILE/ENFILE returned from accept() we disable accept events, and (in case of no accept mutex used) arm timer to re-enable them later. With accept mutex we just drop it, and rely on normal accept mutex handling to re-enable accept events once it's acquired again. As we now handle errors in question, logging level was changed to "crit" (instead of "alert" used for unknown errors).
* update to nginx-1.2.0robert2012-05-13118-1588/+7757
|
* update to 1.0.15robert2012-04-143-71/+213
|
* use a shared stripping function for chroot and make surerobert2012-04-124-14/+16
| | | | | that the path starts with the chroot prefix before doing anything with it
* Set the correct string lengths when stripping the chroot prefixrobert2012-04-043-12/+10
| | | | | | from the paths because ngx_str_set() does not set it correctly for us. This change also avoid a use after free() case which was discovered by sthen@ Based on a diff from Steffen Daode Nurpmeso, tested by me and sthen@
* make sure we strip the chroot prefix from all root variables, not just therobert2012-04-021-7/+8
| | | | first one
* bring back an overwritten change which is essential for the chrootedrobert2012-04-021-1/+9
| | | | version to strip the chroot prefix from root paths
* stupid cvs (dir has 'core' in the name...)sthen2012-03-151-2/+2
|
* resolve conflictssthen2012-03-156-11/+31
|
* update to 1.0.13robert2012-03-0637-243/+236
|
* create the tmp dirs nginx needs for doing proxying inside the chrootrobert2012-02-221-8/+20
| | | | because these get created before the actual chroot happens
* update pcre to 8.30 to be in sync with portsrobert2012-02-1815-1706/+2756
|
* update to 1.0.12robert2012-02-18247-249/+613
|
* update to nginx-1.0.11robert2012-01-0526-284/+535
|
* merge pcre-8.21robert2011-12-146-452/+809
|
* Update to nginx 1.0.10. Bugs fixed include a segmentation fault in a workersthen2011-11-155-12/+14
| | | | process if the resolver receives a large DNS response. OK robert@
* sync to pcre 8.20robert2011-11-128-186/+506
|
* update to 1.0.9robert2011-11-1243-224/+389
|
* Add a flag for nginx (-u) to be able to disable chroot and use a betterrobert2011-10-115-5/+30
| | | | | | method for modifying the document root if chrooted, so currently this allows the user to run the same configuration file with a chrooted and an non-chrooted setup.
* our root is /var/www/htdocs and not /var/www/htmlrobert2011-10-081-1/+1
|
* only strip the full path once and remove any / chars from the begining ofrobert2011-10-081-3/+7
| | | | the path
* Since the worker process of nginx is chrooted on OpenBSD, let's removerobert2011-10-051-0/+4
| | | | | | down the prefix of nginx which is /var/www from the file paths when the worker process tries to reopen files (access.log, error.log, etc.). This fixes the 'nginx -s reopen' issue which was reported by some users.
* update to nginx-1.0.8 which includes many bugfixesrobert2011-10-0323-172/+3149
| | | | for a complete list please check the CHANGES file
* unconditionally chroot to the www user's homedir by defaultrobert2011-09-221-0/+37
|
* fix two signed/unsigned comparsionsrobert2011-09-222-2/+2
|
* thank you CVS for missing the "core" directoryrobert2011-09-2261-0/+21766
|
* import of nginx 1.0.6 with a bundled libpcre needed for pcre to workrobert2011-09-22207-0/+120609
properly. this is not yet linked to the build but we would like to work on it in tree to provide an apache replacement for base