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.

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

Purge content hosting cache 422 response #16

Merged
merged 2 commits into from
Jan 17, 2023

Conversation

rjb1000
Copy link
Contributor

@rjb1000 rjb1000 commented Jan 5, 2023

This is used by the 5GMS AS to indicate that there is something wrong with the request body included in the purgeContentHostingCache operation. For example, the regular expression provided is syntactically invalid.

In this case a 400 (Bad Request) isn't appropriate because the HTTP request was valid. Rather, the syntax error was detected inside the application, i.e. above the Layer 7 application protocol.

This is used by the 5GMS AS to indicate that there is something wrong with the request body included in the purgeContentHostingCache operation. For example, the regular expression provided is syntactically invalid.
TS29571_CommonData.yaml does not include the 422 (Unprocessable Entity) error, so we need to explicitly define it inline.
@rjb1000 rjb1000 merged commit 2cc5028 into main Jan 17, 2023
@davidjwbbc davidjwbbc deleted the purgeContentHostingCache_422-response branch January 25, 2023 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

Successfully merging this pull request may close these issues.

2 participants