Skip to content
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
This repository was archived by the owner on Nov 24, 2025. It is now read-only.

TR should default to using TO API 3.1 #6653

Closed
#6778
Closed
TR should default to using TO API 3.1#6653
#6778
Assignees
rawlinp
Labels
Traffic Routerrelated to Traffic RouterimprovementThe functionality exists but it could be improved in some way.low difficultythe estimated level of effort to resolve this issue is lowlow impactaffects only a small portion of a CDN, and cannot itself break one
Milestone
7.0.0

Description

@rawlinp
rawlinp
opened on Mar 15, 2022

This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components:

  • Traffic Router

Current behavior:

TR defaults to using TO API 2.0 if it doesn't have any profile parameters specifying which API URLs to use.

New behavior:

TR should default to using TO API 3.1 if it doesn't have any profile parameters specifying which API URLs to use.

Metadata

Metadata

Assignees

Labels

Traffic Routerrelated to Traffic RouterimprovementThe functionality exists but it could be improved in some way.low difficultythe estimated level of effort to resolve this issue is lowlow impactaffects only a small portion of a CDN, and cannot itself break one

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions