GitHub user gtenev opened a pull request:

    https://github.com/apache/trafficserver/pull/371

    [ts-4023] cachekey plugin

    This plugin allows some common cache key manipulations based on various 
HTTP request elements. It can
    - sort query parameters so reordering can be a cache hit
    - ignore specific query parameters from the cache key by name or regular 
expression
    - ignore all query parameters from the cache key
    - only use specific query parameters in the cache key by name or regular 
expression
    - include headers or cookies by name
    - capture values from the User-Agent header.
    - classify request using User-Agent and a list of regular expressions

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gtenev/trafficserver ts-4023

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/371.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #371
    
----
commit 0dc9f5723ce5ee4b1afe9b7cd52f35cba77afac3
Author: Gancho Tenev <gtte...@gmail.com>
Date:   2015-11-13T22:03:17Z

    [ts-4023] cachekey plugin
    
    This plugin allows some common cache key manipulations based on various 
HTTP request elements. It can
    - sort query parameters so reordering can be a cache hit
    - ignore specific query parameters from the cache key by name or regular 
expression
    - ignore all query parameters from the cache key
    - only use specific query parameters in the cache key by name or regular 
expression
    - include headers or cookies by name
    - capture values from the User-Agent header.
    - classify request using User-Agent and a list of regular expressions

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to