commit | ab9929e5a5c631353a7eac4c49543aa8756d5e7a | [log] [tgz] |
---|---|---|
author | Otto van der Schaaf <oschaaf@we-amp.com> | Wed Aug 20 20:32:09 2014 +0200 |
committer | Jeffrey Crowell <jcrowell@google.com> | Fri Oct 24 16:23:45 2014 -0400 |
tree | fadf53f710c2483cd63e8d74f96683d272954a0b | |
parent | 9832a049fe56c7537c785be8d563562c45c0a03c [diff] |
native fetcher: Support http keep-alive Based on @dinic his work, add keep-alive support for the native fetcher. Adds a new option, usable at the http{} level in configuration: pagespeed NativeFetcherMaxKeepaliveRequests 50; The default value is 100 (aligned to nginx). Setting the value to 1 turns off keep-alive requests altogether). Most notable changes: - Request keep-alive by adding the appropriate request header - Fixes connections getting reused while they are servicing other requests: - Remove connection from the pool of available connections for keepalive when applicable - Disable keepalive in more appropriate situations - Response parsing fixes - Remove connections that timeout from the k.a. pool - Add a few sanity (D)CHECKS - Emit debug messages for traceability - Fix for ignoring ipv6 addresses returned from dns queries when ipv6 is enabled. - Bump the fetch timeout in test configuration to deflake tests that require dns lookups (which will be done via 8.8.8.8 currently for the native fetcher) Conflicts: src/ngx_fetch.cc
ngx_pagespeed speeds up your site and reduces page load time by automatically applying web performance best practices to pages and associated assets (CSS, JavaScript, images) without requiring you to modify your existing content or workflow. Features include:
To see ngx_pagespeed in action, with example pages for each of the optimizations, see our demonstration site.
Follow the steps on build ngx_pagespeed from source.
Follow the steps on PageSpeed configuration.
For feedback, questions, and to follow the progress of the project: