Opened 11 years ago
Closed 11 years ago
#556 closed defect (fixed)
SECORE HTTP exit codes for exception reports not to be 200
Reported by: | Piero Campalani | Owned by: | Dimitar Misev |
---|---|---|---|
Priority: | major | Milestone: | 9.0 |
Component: | undecided | Version: | development |
Keywords: | exit code http exception | Cc: | Dimitar Misev, Peter Baumann |
Complexity: | Easy |
Description
SECORE always returns 200 OK HTTP status.
E.g. running:
$ wget "http://localhost:8090/def/crs?authority=EPSG&version=0&code=4327&foo=qwerty" -O file --2013-11-22 20:18:49-- http://localhost:8090/def/crs?authority=EPSG&version=0&code=4327&foo=qwerty Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:8090... connected. HTTP request sent, awaiting response... 200 OK ...
Whereas it should return 400 Bad request (or 404 Not Found..?), in this case.
Change History (3)
comment:1 by , 11 years ago
Status: | new → accepted |
---|
comment:3 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Note:
See TracTickets
for help on using tickets.
Patch submitted.