Opened 12 years ago
Closed 11 years ago
#389 closed enhancement (fixed)
SECORE exception when mandatory parameter is missing
Reported by: | Piero Campalani | Owned by: | mrusu |
---|---|---|---|
Priority: | minor | Milestone: | 9.0 |
Component: | secore | Version: | 8.4 |
Keywords: | secore exception text | Cc: | |
Complexity: | Medium |
Description
Although SECORE throws exception when you don't provide a mandatory parameter (authority|version|code) in a KVP URI, it returns a misleading exception:
http://localhost:8080/def/crs?authority=EPSG&version=0
<ows:ExceptionText>Operation not defined</ows:ExceptionText>
Like is done in this example (which in turn maybe should better alert that foo
is an illegal parameter):
http://localhost:8080/def/crs?authority=EPSG&version=0&foo=4327
<ows:ExceptionText>Insufficient parameters provided</ows:ExceptionText>
Change History (2)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I fixed the first case, but that foo is an illegal parameter is not possible as there's no distinction for parameterized CRS.