Replace Fastly VCL cstr_escape w/ json.escape #5065
Merged
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.
Purpose of this pull request
Bring Sumo Logic's Fastly integration VCL examples in line with Fastly's own documentation for integrating with Sumo Logic. This concerns the preferred use of the VCL
json.escapefunction over the somewhat ineffective (in the context of JSON) use of the suggestedcstr_escape.TL:DR Using
cstr_escapein a Fastly VCL log format string may still result in invalid JSON sequences, whereas substitutingjson.escapewill alleviate all those issues.Select the type of change
Ticket (if applicable)
Originated by Fastly.