Skip to content

@RequestMapping no longer agnostic about URL path parameters [SPR-10234] #14867

@spring-projects-issues

Description

@spring-projects-issues

Anthony Gerrard opened SPR-10234 and commented

@RequestMapping("/something")

used to match

/something;else=true

in Spring 3.1. In Spring 3.2 you now get a 404 not found. This is inconsistent with the behaviour demanded in the servlet 3.0 specification (not sure if this counts for anything)

The path used for mapping to a servlet is the request URL from the request object minus the context path and the path parameters

I notice jsessionid path parameters are still ignored.


Affects: 3.2 GA

Issue Links:

Referenced from: commits 9c19469, 5b1165b, d23de28

Metadata

Metadata

Assignees

Labels

in: webIssues in web modules (web, webmvc, webflux, websocket)type: bugA general bug

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions