Giters

azavea / nasa-hyperspectral

An event-driven image processing pipeline for developing our foundational capability to work with HSI data sources.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Fix header issues in franklin

moradology opened this issue · comments

commented

The stac-api validator is throwing some issues mostly related to headers and correct response codes. The fix should only require a few modifications but these issues appear to be present in pre-pgstac Franklin:

(stac-api-validator) (base) cholmes@x9t37m3hgt stac-api-validator % python stac_api_validator/validate.py --root http://ec2-34-239-128-44.compute-1.amazonaws.com/

Validating http://ec2-34-239-128-44.compute-1.amazonaws.com/

STAC API - Core conformance class found.

STAC API - Features conformance class found.

STAC API - Item Search conformance class found.

STAC API - Item Search Fields extension conformance class found.

warnings:

  • / : Link[rel=service-doc] must exist

  • GET Search with datetime=/1984-04-12T23:20:50.52Z/1985-04-12T23:20:50.52Z returned status code 200 instead of 400

  • GET Search with datetime=/1984-04-12T23:20:50.52Z/1985-04-12T23:20:50.52Z/ returned status code 200 instead of 400

errors:

  • / : Link[rel=root] must exist

  • service-desc ({'href': 'http://ec2-34-239-128-44.compute-1.amazonaws.com/open-api/spec.yaml', 'rel': 'service-desc', 'type': 'application/vnd.oai.openapi+json;version=3.0', 'title': 'Open API 3 Documentation'}): link must advertise same type as endpoint content-type header, advertised 'application/vnd.oai.openapi+json;version=3.0', actually 'text/plain; charset=UTF-8'

  • Search (http://ec2-34-239-128-44.compute-1.amazonaws.com/search): must have content-type header 'application/geo+json', actually 'application/json'

  • GET Search with {'limit': -1} returned status code 200, must be 400

  • POST Search with {'limit': -1} returned status code 200, must be 400

  • GET Search with {'limit': 0} returned status code 200, must be 400

  • POST Search with {'limit': 0} returned status code 200, must be 400

  • GET Search with {'limit': 10001} returned status code 200, must be 400

  • POST Search with {'limit': 10001} returned status code 200, must be 400

  • GET Search with bbox and intersects returned status code 200

  • POST Search with bbox and intersects returned status code 200

  • GET Search with bbox=param (lat 1 > lat 2) returned status code 200, instead of 400

  • POST Search with bbox: [100.0, 1.0, 105.0, 0.0] (lat 1 > lat 2) returned status code 200, instead of 400

  • GET Search with bbox=0,0,0,1,1 returned status code 200, instead of 400

  • GET Search with bbox=0,0,0,1,1,1,1 returned status code 200, instead of 400

  • GET Search with datetime=2000-02-02T00:00:00Z extracted from an Item returned status code 400

  • GET Search with datetime=1985-04-12T23:20:50.52Z returned status code 400

  • GET Search with datetime=1996-12-19T16:39:57-00:00 returned status code 400

  • GET Search with datetime=1996-12-19T16:39:57+00:00 returned status code 400

  • GET Search with datetime=1996-12-19T16:39:57-08:00 returned status code 400

  • GET Search with datetime=1996-12-19T16:39:57+08:00 returned status code 400

  • GET Search with datetime=1985-04-12T23:20:50.52Z/1986-04-12T23:20:50.52Z returned status code 400

  • GET Search with datetime=1985-04-12T23:20:50.52+01:00/1986-04-12T23:20:50.52+01:00 returned status code 400

  • GET Search with datetime=1985-04-12T23:20:50.52-01:00/1986-04-12T23:20:50.52-01:00 returned status code 400

  • GET Search with datetime=1937-01-01T12:00:27.87+01:00 returned status code 400

  • GET Search with datetime=1985-04-12T23:20:50.52Z returned status code 400

  • GET Search with datetime=1937-01-01T12:00:27.8710+01:00 returned status code 400

  • GET Search with datetime=1937-01-01T12:00:27.8+01:00 returned status code 400

  • GET Search with datetime=1937-01-01T12:00:27.8Z returned status code 400

  • GET Search with datetime=2020-07-23T00:00:00.000+03:00 returned status code 400

  • GET Search with datetime=2020-07-23T00:00:00+03:00 returned status code 400

  • GET Search with datetime=1985-04-12t23:20:50.000z returned status code 400

  • GET Search with datetime=2020-07-23T00:00:00Z returned status code 400

  • GET Search with datetime=2020-07-23T00:00:00.0Z returned status code 400

  • GET Search with datetime=2020-07-23T00:00:00.01Z returned status code 400

  • GET Search with datetime=2020-07-23T00:00:00.012Z returned status code 400

  • GET Search with datetime=2020-07-23T00:00:00.0123Z returned status code 400

  • GET Search with datetime=2020-07-23T00:00:00.01234Z returned status code 400

  • GET Search with datetime=2020-07-23T00:00:00.012345Z returned status code 400

  • GET Search with datetime=2020-07-23T00:00:00.0123456Z returned status code 400

  • GET Search with datetime=2020-07-23T00:00:00.01234567Z returned status code 400

  • GET Search with datetime=2020-07-23T00:00:00.012345678Z returned status code 400