health check supported fastcgi
Changed check_fastcgi_params to check_fastcgi_params
Added the documents of check_fastcgi
Fixed the style of fastcgi_check document
consistent_hash和session_sticky模块支持ssl session保持
type error
Merge pull request #463 from dinic/ssl_session

consistent_hash和session_sticky模块支持ssl session保持
Add .travis.yml for travis-ci.org testing

http://docs.travis-ci.com/user/getting-started/

If we link travis-ci.org to https://github.com/alibaba/tengine,
we can perform continuous testing against new commits to ensure
they do not break the build. travis-ci.org is a free service.

This commit provides an appropriate configuration file to tell
travis-ci.org about tengine and how we build it from source.
Merge pull request #466 from Jamyn/master

Add .travis.yml for travis-ci.org testing
Core: slab allocator free pages defragmentation.

Merge nginx official patch: http://hg.nginx.org/nginx/rev/c46657e391a3
Merge pull request #468 from chobits/slab_merge

slab allocator free pages defragmentation
Merge pull request #385 from yzprofile/fastcgi_cheack

health check supported fastcgi
Fixed: fastcgi_check compatible with new health check module
Merge pull request #474 from yzprofile/master

Fixed: fastcgi_check compatible with new health check module
Feature: rt support in sysguard module

Two new directives are introduced:
*) sysguard_mode and/or
*) sysguard_rt rt=time period=time action=some_location

This feature introduces the ability to limit requests based on "rt".
Also, all the measurements can be considered in an "and" or "or"
relationship due to the new "sysguard_mode" directive.

Test cases are included.

Signed-off-by: Paul Yang(InfoHunter) <paulyang.inf@gmail.com>
Merge pull request #476 from InfoHunter/sysguard-rt.final

Feature: rt support in sysguard module
SPDY/3: drop the "delayed" flag when finalizing connection

This problem has been fixed for SPDY/2.
More details are available here: http://hg.nginx.org/nginx/rev/a279d2a33dbf
Merge pull request #489 from chobits/master

SPDY/3: drop the "delayed" flag when finalizing connection
Feature: upstream dynamic resolve

This is version 1, the "imperfect" version.

Introduces a new directive with two parameters into upstream context:

Directive:
    *) dynamic_resolve: enables dynamic resolving functionality on an upstream.

Parameters:
    *) fail_timeout=time, specifies how long tengine will not launch
       a dns query if the dns server is down.
    *) fallback=action, specifies what action to take if the dns server is
       considered as "down".

Support:
    *) use the first result of a dns response
    *) fail_timeout
    *) fallback action, but the action "stale" is limited to use what tengine gets
       when it parses the configuration

Not Support:
    *) all results from a dns response
    *) ipv6 address
    *) using stale dns data

All "Not support" stuff are now supported in "perfect" version, which
will be released after tengine is upgraded to original nginx 1.6.x
branch.

Test cases are included.

Signed-off-by: Paul Yang(InfoHunter) <paulyang.inf@gmail.com>
Bugfix: /etc/resolv.conf parsing error with ipv6.
Merge pull request #496 from lifeibo/master

Bugfix: /etc/resolv.conf parsing error with ipv6.