-
Notifications
You must be signed in to change notification settings - Fork 343
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.
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
Added an HTTP-Header equivalent for 'format' TR Query Param #3554
base: master
Are you sure you want to change the base?
Conversation
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
8d90bee
to
48863dd
Compare
Refer to this link for build results (access rights to CI server needed): |
48863dd
to
4731c5f
Compare
Refer to this link for build results (access rights to CI server needed): |
4731c5f
to
0d8d639
Compare
0d8d639
to
b05a01d
Compare
b05a01d
to
85f289e
Compare
0660787
to
89982cf
Compare
8a0dd1c
to
f99e7b2
Compare
16553cc
to
61e63bc
Compare
61e63bc
to
5393e62
Compare
5393e62
to
9ada668
Compare
9ada668
to
243bacc
Compare
What does this PR (Pull Request) do?
Adds the
X-TC-Format
HTTP Header as an alternative to/equivalent of theformat
query parameter for TR to use in formatting responses to requests to STEERING Delivery Services.Accepts either
json
(for compatibility with the query parameter) orapplication/json
(for compatibility with HTTP content negotiation) to format response as JSON.Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
You could run the TR unit tests, as well as verifying that TR responses to STEERING requests are properly formatted when
X-TC-Format
is given and set to a valid value.The following criteria are ALL met by this PR