-
Notifications
You must be signed in to change notification settings - Fork 37.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PathMatchingResourcePatternResolver
can no longer handle paths containing spaces and special characters
#30031
Comments
This is a regression introduced in dbf3609. See spring-projects/spring-boot#34379 for further details. |
Thanks for reporting the regression. The cause for the regression is that Consequently, We'll look into it and provide a fix in |
Possible solution outlined by @JoeyBling in #29934 (comment). |
PathMatchingResourcePatternResolver
can no longer handle paths containing spaces
This also happens if the path contains other chars like |
PathMatchingResourcePatternResolver
can no longer handle paths containing spacesPathMatchingResourcePatternResolver
can no longer handle paths containing spaces and special characters
Yes, we are aware that it is a general decoding issue. I've updated the title of this issue to reflect that. Thanks for prompting that. |
Also raising the log level to warn for file system retrieval failures. Closes spring-projectsgh-30031
Affects: spring-core : 6.0.5
When the spring application is in a directory that contains a space, it skips probably all @ComponentScan-based bean creations (I am sure it skips all
@Configuration
classes, and I suspect it also skips all@RestController
s as well, so it is a pretty safe bet to assume that it skips everything else as well):Functionality was working fine with 6.0.4.
Also, log level either in the line above, or somewhere close by must be ERROR, not DEBUG.
The text was updated successfully, but these errors were encountered: