Skip to content

fix: REST errors answering 500 depending on the jar order in WEB-INF/lib - #1591

Open
groldan wants to merge 1 commit into
GeoWebCache:mainfrom
groldan:fix/rest-exception-handler-order
Open

groldan wants to merge 1 commit into
GeoWebCache:mainfrom
groldan:fix/rest-exception-handler-order

Conversation

@groldan

@groldan groldan commented Sep 22, 2026

Copy link
Copy Markdown
Member

Make RestExceptionHandler answer every RestException with the status of the exception regardless of the jar order.

Otherwise GeoServer's RestControllerAdvice may take precedence and return 500 instead of 404/400.

Fixes #1590

Note camptocamp/python-geoservercloud#219 made python librart used for acceptance tests resilient to the current behaviour. This is the proper fix.

Make RestExceptionHandler answer every RestException with the status of the
exception regardless of the jar order.

Otherwise GeoServer's RestControllerAdvice may take precedence and
return 500 instead of 404/400.
@groldan groldan self-assigned this Sep 22, 2026
@groldan groldan changed the title Stop REST errors answering 500 depending on the jar order in WEB-INF/lib fix: REST errors answering 500 depending on the jar order in WEB-INF/lib Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

REST errors return 500 when Spring registers GeoServer's catch-all @ControllerAdvice before RestExceptionHandler

1 participant