ASF GitHub Bot logged work on TS-4959:

                Author: ASF GitHub Bot
            Created on: 12/Oct/16 21:33
            Start Date: 12/Oct/16 21:33
    Worklog Time Spent: 10m 
      Work Description: GitHub user zwoop opened a pull request:


    TS-4959: Remove remnants of old UA configurations and handling

    I made this as two commits:
    1) Remove some definitely strange code around MSIE.
    2) Remove all the code around the accept_encoding_filter_enabled.
    For #2, this configuration doesn't actually exist in RecordsConfig.cc, and 
it's also missing all possible ways of configuring the regular expressions that 
it needs. So I figured, we can just nuke it :).

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

    $ git pull https://github.com/zwoop/trafficserver TS-4959

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


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

    This closes #1101
commit 2e2fad5dc67999f0831f8481b61e04408844228c
Author: Leif Hedstrom <zw...@apache.org>
Date:   2016-10-12T19:51:08Z

    TS-4959: Remove remnants of an old browser

commit 25b7900a4574edf9b11bcb02307e02a310e80c41
Author: Leif Hedstrom <zw...@apache.org>
Date:   2016-10-12T21:18:24Z

    TS-4959: Remove remnants of an configuration / UA


Issue Time Tracking

            Worklog Id:     (was: 30534)
            Time Spent: 10m
    Remaining Estimate: 0h

> Remove an old remnant of MSIE UA detection
> ------------------------------------------
>                 Key: TS-4959
>                 URL: https://issues.apache.org/jira/browse/TS-4959
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: 7.1.0
>          Time Spent: 10m
>  Remaining Estimate: 0h
> This might have been part of an old option as well, that seems to have been 
> removed (so this code was likely left around by mistake).

This message was sent by Atlassian JIRA

Reply via email to