Opened 4 years ago

Closed 4 years ago

#356 closed defect (fixed)

SECORE does not report exception when an invalid parameter name is set on a non-parametrized CRS

Reported by: pcampalani Owned by: dmisev
Priority: minor Milestone: 9.0
Component: secore Version: 8.4
Keywords: invalid parameters Cc: dmisev, mrusu
Complexity: Easy


When wrong parameters are set in a URI of a parametrized CRS, SECORE properly reports an error (e.g. see "'foo'")

When handling normal single URIs, it is probably better and clearer if SECORE returns an exception not only when one amongst authority, version, code have typos, but also when one or more additional KV-pairs are set in the URI, e.g. "'foo'".

Change History (2)

comment:1 Changed 4 years ago by dmisev

  • Owner changed from mrusu to dmisev
  • Status changed from new to assigned

An error is now reported. Regular non-parameterized CRS should not have any extra parameters, besides the special expand one.

<ows:ExceptionReport version="2.0.0" xsd:schemaLocation="" xmlns:ows="" xmlns:xsd="" xmlns:xlink="">
  <ows:Exception exceptionCode="InvalidRequest">
    <ows:ExceptionText>Expected parameterized CRS definition, but http://localhost:8080/def/crs/EPSG/0/4327?foo=qwerty points to GeodeticCRS. Identifiers of simple definitions are not supposed to contain extra parameters, aside from the authority, version and code.</ows:ExceptionText>

comment:2 Changed 4 years ago by dmisev

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.