DTP open sourcing #7161
Merged
DTP open sourcing #7161
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
There was a problem hiding this comment.
CodeQL found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.
zrhoffman
added
new feature
ocket8888
added
medium impact
zrhoffman
added
the
experimental
zrhoffman
requested changes
Nov 1, 2022
| alog.Printf("%.3f %s \"%s\" %s %d b=%d ttms=%d uas=\"%s\" rr=\"%s\"\n", | ||
| float64(timeStart.UnixNano())/float64(1.e9), | ||
| r.Method, | ||
| r.URL.String(), |
Check failure
Code scanning / CodeQL
Log entries created from user input
zrhoffman
approved these changes
Nov 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR open sources our internal testing tool, DTP. Originally DTP was a stand alone origin that can provide origin responses based on path values to simulate a variety of scenarios. It made sense to include this as another endpoint type within fakeOrigin to expand it's capabilities. There is a new endpoint type of "testing" which adds this functionality.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Build the fakeOrigin and create a testing endpoint and issue some curls against it
PR submission checklist