Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TO/TP - query string handling options force cacheurl on option 1 #1554

Closed
ezelkow1 opened this issue Nov 16, 2017 · 1 comment
Closed

TO/TP - query string handling options force cacheurl on option 1 #1554

ezelkow1 opened this issue Nov 16, 2017 · 1 comment
Labels
bug something isn't working as intended high impact impacts the basic function, deployment, or operation of a CDN Traffic Portal v1 related to Traffic Portal version 1
Milestone
2.2.0

Comments

@ezelkow1
Copy link
Member

If option 1 is chosen on the query string handling for a delivery service in TO or TP this will force an insertion of a generic cacheurl line which uses a default qstring.config file. When we eventually switch to ATS7 this will break all DS's using this option since cacheurl will no longer work and cachekey must be used
@mitchell852 mitchell852 added critical Traffic Portal v1 related to Traffic Portal version 1 labels Dec 4, 2017
@rob05c rob05c added the bug something isn't working as intended label Jan 26, 2018
@rob05c rob05c added this to the 2.2.0 milestone Jan 26, 2018
@rob05c
Copy link
Member

rob05c commented Jan 29, 2018

Fixed in #1602

@rob05c rob05c closed this as completed Jan 29, 2018
@mitchell852 mitchell852 added the high impact impacts the basic function, deployment, or operation of a CDN label Nov 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug something isn't working as intended high impact impacts the basic function, deployment, or operation of a CDN Traffic Portal v1 related to Traffic Portal version 1
Projects
None yet
Milestone
2.2.0
Development

No branches or pull requests
3 participants
@mitchell852 @rob05c @ezelkow1