search

5G-MAG / Standards

Specifications related to 5G-MAG's areas of work. Tracking comments, bug-fixing, request for new features, etc.
https://www.5g-mag.com/standards
11 stars 2 forks source link

Inadvisable use of response code 422 (Unprocessable Entity) by 5GMS AF at reference point M1 #94

Closed rjb1000 closed 4 months ago

rjb1000 commented 9 months ago

Context

In TS 26.512 V17.6.0:

  1. Clause 4.3.5.2 specifies the use of the HTTP response code 422 (Unprocessable Entity) in the error case where the media type of a Content Preparation Template is not supported by the 5GMS AF. The OpenAPI YAML at clause C.3.3 does not include this response code.
  2. Clause 7.6.4.3 specifies the use of the HTTP response code 422 (Unprocessable Entity) in the error case where the regular expression for cache purging is syntactically malformed. The OpenAPI YAML at clause C.3.5 is consistent with this specification.

Description

General consensus (e.g. here) is that usage of the HTTP response code 422 (Unprocessable Entity) should be limited to WebDAV and that 400 (Bad Request) is likely to be more appropriate in most cases, despite that fact that this latter response code is more intended to signal a malformed HTTP request than a malformed message body.

Suggested solution

  1. Respecify the use of 400 (Bad Request) in clause 4.3.5.2 and add this to the Content Preparation Templates creation operation in clause C.3.3.
  2. Respecify the use of 400 (Bad Request) in clause 7.6.4.2 and modify the cache purge operation in clause C.3.5 for consistency.
rjb1000 commented 8 months ago

Change Request addressing this issue endorsed during yesterday's 3GPP SA4 ad hoc call:

Revisions to be contributed to SA4#126 (Chicago).

rjb1000 commented 7 months ago

Change Requests agreed at SA4#126 (Chicago):

Changes in clause 4.3.4.2, 4.3.5.4 and 7.6.4.3.

rjb1000 commented 4 months ago

CR Packs approved at SA#102 (Edinburgh):

rjb1000 commented 4 months ago