Opened 12 years ago
Closed 11 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: | Piero Campalani | Owned by: | Dimitar Misev |
---|---|---|---|
Priority: | minor | Milestone: | 9.0 |
Component: | secore | Version: | 8.4 |
Keywords: | invalid parameters | Cc: | Dimitar Misev, mrusu |
Complexity: | Easy |
Description
When wrong parameters are set in a URI of a parametrized CRS, SECORE properly reports an error (e.g. see "http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0.1/ANSI-Date?nonsense='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. "http://kahlua.eecs.jacobs-university.de:8080/def/crs/EPSG/0/32633?nonsense='foo'"
.
Change History (2)
comment:1 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
An error is now reported. Regular non-parameterized CRS should not have any extra parameters, besides the special expand one.