[jira] [Updated] (TC-363) cacheurl_qstring.conf file is not generated when qstringIgnore=1 and location profile parameter is missing for edge/mid cache

["Ryan Durfey (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TC-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan Durfey updated TC-363:
---------------------------
         Labels: Configuration  (was: )
    Component/s: Traffic Ops
        Summary: cacheurl_qstring.conf file is not generated when qstringIgnore=1 and location profile parameter is missing for edge/mid cache  (was: TrafficOps: cacheurl_qstring.conf file is not generated when qstringIgnore=1 and location profile parameter is missing for edge/mid cache)

> cacheurl_qstring.conf file is not generated when qstringIgnore=1 and location profile parameter is missing for edge/mid cache
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TC-363
>                 URL: https://issues.apache.org/jira/browse/TC-363
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Ops
>    Affects Versions: 2.1.0
>            Reporter: Robert Scrimo
>              Labels: Configuration
>
> {{cacheurl_qstring.conf}} file is not generated when {{qstringIgnore=1}} and {{location}} profile parameter for config file {{cacheurl_qstring.config}} is missing for edge/mid cache profile.  This is a issue because {{remap.config}} references this non-existent file.
> {quote}
> e.g. map	http://edge-cache.http-ds.mycdn.somedomain.com/     http://origin-server.somedomain.com/ @plugin=header_rewrite.so @pparam=dscp/set_dscp_0.config @plugin=cacheurl.so @pparam=cacheurl_qstring.config
> {quote}
> The workaround is to add {{location}} parameter for {{cacheurl_qstring.config}} config file to the edge/mid cache profile. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)