Skip to content

ErrorController not called for non existing APIs after upgrade to Spring Boot 3.3.3(from 2.7.0) #44150

Closed as not planned
@jirou97

Description

@jirou97

Issue: ErrorController Not Called After Upgrading to Spring Boot 3.3.3

Hello everyone, this is my first time raising an issue, so please be patient with me.

Problem Description

After upgrading from Spring Boot 2.7.0 to 3.3.3, the ErrorController implementation is no longer called for non-existing APIs.
This worked fine in Spring Boot 2.7.0.

Reproduction

I have attached two demos that reproduce this issue.
You can run the test and see in the 3.3.3 version that the non-existing API returns 404 NOT FOUND instead of calling the ErrorController.

demo-spring-boot-2.7.0.zip
demo-spring-boot-3.3.3.zip

Could you investigate what is the source of this behaviour?

Thanks ☮

Metadata

Metadata

Assignees

No one assigned

    Labels

    for: stackoverflowA question that's better suited to stackoverflow.comstatus: invalidAn issue that we don't feel is valid

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions