Camunda can't map paths without a trailing slash

[GabrielJuliao]

Environment (Required on creation)

Camunda Spring Boot Starter

Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)

Camunda can't map paths without a trailing slash. The issue was found in an existing application, however, it can be reproduced with a freshly generated project. With the below configuration:

Observed Behavior (Required on creation)

As you can see below, if you don't send the request with a trailing slash, camunda can't map the path and returns a 404.

The following paths result in a 404 error:

• localhost:8080/camunda/app
• localhost:8080/camunda/app/cockpit
• localhost:8080/camunda/app/admin
• localhost:8080/camunda/app/tasklist
• localhost:8080/camunda/app/welcome

Expected behavior (Required on creation)

Camunda handles the request regardless of the presence or absence of a trailing slash.

Root Cause (Required on prioritization)

Spring Boot 3 does not automatically match trailing slashes anymore, and the option to enable it is deprecated. See corresponding issue.
The registered filters and redirect mappings are registered for paths including the trailing slashes.

Solution Ideas

1. Register a filter that includes a trailing slash if not present already. It should probably be placed early in the filter chain. Maybe directly after setting the app path.
2. Add redirect mappings for the failing paths:

registry.addRedirectViewController(applicationPath + "/app", applicationPath + "/app/");
registry.addRedirectViewController(applicationPath + "/app/**", applicationPath + "/app/**/");

Tasks

Preview Give feedback

1. chore(spring-boot-webapp): introduce filter to make URLs without trailing slashes work #3947
   ci:spring-boot scope:spring-boot +2
   
2. https://github.com/camunda/camunda-bpm-platform-maintenance/pull/1109
3. https://github.com/camunda/camunda-bpm-platform-maintenance/pull/1110

[mboskamp]

HI @GabrielJuliao,
Thank you for opening this bug report. It seems you removed the section headers from the template, which made it a bit hard to read. I tried to add them again. Could you please check if I got you right?

Regarding the issue you were facing. We will try to reproduce it and check the root-cause. If you are up to providing a pull request, we will gladly accept it. In that case, please let me know by adding a comment here. I can assist you with questions if necessary.

Cheers,
Miklas

[mboskamp]

Assigned to @tasso94 for prioritization.

[tasso94]

Hi @mboskamp,

Thanks for root causing this and for providing solution ideas.

Scheduled for one of the next patch releases and 7.21.0.

[mboskamp]

@tasso94 raised the following points:

• We should avoid having two places where we define paths.
• The filter should only apply to the few broken paths. For example, a request to /foo/bar/baz/app/admin should not invoke the filter.

I removed the paths list in the filter and instead registered the filter for all the paths we want to redirect.