mmisw / mmiorr

Unmaintained old MMI ORR system (v2) -- New development at https://github.com/mmisw/orr
2 stars 1 forks source link

empty reponse with incorrect content type #284

Closed mmisw closed 9 years ago

mmisw commented 9 years ago

From caru...@gmail.com on October 06, 2010 09:46:36

What steps will reproduce the problem? 1. do a query given an empty result, eg. SELECT ?prop ?value WHERE { < http://example.org/foo/baz > ?prop ?value . } What is the expected output? The empty response in the appropriate format, for example, if the response is HTML, then, with an indication that the response was empty AND with the "text/html" content type What do you see instead? empty response but with "httpd/unix-directory" content type Please use labels and text to provide additional information.

Original issue: http://code.google.com/p/mmisw/issues/detail?id=284

mmisw commented 9 years ago

From caru...@gmail.com on October 06, 2010 11:25:35

When fixed, the following general behavior should be expected:

\ When issuing the query against http:.../ont?query resulting in empty responses:

For format HTML: An HTML page with the empty contents (might be the usual table with only the column headers). Content type: "text/html"

For format RDF/XML:

Example query: CONSTRUCT {< http://example.org/foo/baz > ?prop ?value } WHERE { < http://example.org/foo/baz > ?prop ?value . }

Similar behavior for other formats.

\ When doing requests for (non-existing) terms (note that these are dispatched internally with SPARQL queries):

The response should always be 404 (not found) regardless of the requested format. Examples: Request: http://mmisw.org/ont/auth/vocab/nonexistentterm.rdf Response: 404 (not found)

Request: http://mmisw.org/ont/?uri=http://example.org/foo/baz Response: 404 (not found)

Status: Started
Labels: -Priority-Medium Priority-High query

mmisw commented 9 years ago

From caru...@gmail.com on October 06, 2010 12:57:49

Fixed. MMI Ontology and Term URI Resolver. Version 2.0.10.beta (201010061255)

Status: Fixed