[Requests] Comments on OGC Web Services Common Standard 1.2

Ethan Davis edavis at unidata.ucar.edu
Wed May 20 17:45:34 EDT 2009


1. Evaluator:

Ethan Davis
UCAR Unidata
edavis at unidata.ucar.edu

2. Submission:

06-121r7, OGC Web Service Common Standard 1.2

PART B (1)

1. Requirement:

Increase flexibility in the HTTP status codes allowed with a response
body containing an OGC exception report with "NoApplicableCode"
exception code.

2. Implementation Specification Section number:

Section 8.6 "HTTP STATUS codes for OGC Exceptions" Table 28, expand the
entry for "NoApplicableCode" to allow for any HTTP status code from the
3xx, 4xx, and 5xx classes of HTTP status codes.

3. Criticality:


4. Comments/justifications for changes:

For data that has aged off of a rolling archive, the "NoApplicableCode"
exception code is the most applicable but a 404 (Not Found) HTTP status
code is more appropriate and descriptive than a 500 (Internal Server
Error) HTTP status code. A non-empty HTTP response body is also
appropriate for many of the HTTP redirect status codes (3xx) and client
error status codes (4xx). Expanding the allowed HTTP status codes to go
with a "NoApplicableCode" OGC exception would allow for OGC content in
these situations.

PART B (2)

1. Requirement:

Expand subclause 11.7 "HTTP responses" to clarify the use of HTTP status
codes in conjunction with section 8.6 "HTTP STATUS codes for OGC Exceptions"

2. Implementation Specification Section number:

11.7 "HTTP responses"

3. Criticality:


4. Comments/justifications for changes:

Sublause 8.6 was expanded to discuss HTTP status codes but subclause
11.7 has not been updated to match.

Some possible content:

    11.7 HTTP responses

    11.7.1 Introduction

    <first paragraph and note of existing 11.7>

    11.7.2 HTTP status codes

    A successful response to a valid request must include a
    200 HTTP status code. A response containing an exception
    report must include an HTTP status code as detailed in
    Table 26 in subclause 8.6.

   Clients must recognize and handle the 200 status code as
   well as those listed in Table 26. Clients should recognize
   and handle other HTTP status codes as well, e.g., HTTP
   redirect codes (301, 302, 307). Though clients do not need
   to understand all status codes they must (according to the
   HTTP specification [IETF RFC 2616], section 6.1.1)
   understand the class of any response code. For instance,
   if a client receives a status code 401 but does not
   understand that code it must handle that response as a
   4xx "Client Error".

   <HTTP redirect paragraph from existing 11.7>

   Servers may send other HTTP status codes defined in
   [IETF RFC 2616] as appropriate for the situation and with
   appropriate HTTP response headers and HTTP response body
   as specified for the HTTP status code being returned.

   11.7.3 HTTP Response body

   <the rest of the existing 11.7 section>



Ethan R. Davis                                Telephone: (303) 497-8155
Software Engineer                             Fax:       (303) 497-8690
UCAR Unidata Program Center                   E-mail:    edavis at ucar.edu
P.O. Box 3000
Boulder, CO  80307-3000                       http://www.unidata.ucar.edu/

More information about the Requests mailing list