Issue 17238: GET  operation on non-existing baseURL or sectionpath SHOULD return 404 status code (hdata-ftf)
Source: MITRE (Mr. Jason Mathews, mathews(at)mitre.org)
Nature: Clarification
Severity: Minor
Summary: 6.4.1 defines a GET with a 200 for success but doesn't address the not found case as defined in other GET operations (e.g. 6.2.1 and 6.5.1)


The implied requirement here is the following, which should be added to the section:


If baseURL does not exist or no sectionpath of name sectionpath exists, the implementation SHOULD (or MUST) return a HTTP status code 404.

This would then be consistent with section 6.5.1 for an invalid/non-existing documentname in the URL
Resolution: 
Revised Text: 
Actions taken:
March 13, 2012: received issue
Discussion: 


End of Annotations:=====

m: webmaster@omg.org
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Jason Mathews
Employer:        MITRE
mailFrom:        mathews@mitre.org
Terms_Agreement: I agree
Specification:   OMG hData RESTful Transport
Section:         6.4.1
FormalNumber:    dtc/2012-01-03
Version:         1.0
Doc_Year:        2012
Doc_Month:       January
Doc_Day:         Day
Page:            5
Title:           GET  operation on non-existing baseURL or sectionpath SHOULD return 404 status code
Nature:          Clarification
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


6.4.1 defines a GET with a 200 for success but doesn't address the not found case as defined in other GET operations (e.g. 6.2.1 and 6.5.1)


The implied requirement here is the following, which should be added to the section:


If baseURL does not exist or no sectionpath of name sectionpath exists, the implementation SHOULD (or MUST) return a HTTP status code 404.

This would then be consistent with section 6.5.1 for an invalid/non-existing documentname in the URL.