PathResourceResolver.getResource() does not log warning if Resource#getURL() throws exception
#31624
Assignees
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: backport
An issue that is a backport of another issue to a maintenance branch
type: bug
A general bug
Milestone
Comments
github-actions
bot
added
in: web
sbrannen
added a commit
that referenced
this issue
Nov 20, 2023
Prior to this commit, the getResource() methods in PathResourceResolver implementations allowed an exception thrown from Resource#getURL() to propagate instead of logging a warning about the missing resource as intended. This commit modifies the getResource() methods in PathResourceResolver implementations so that the log messages include the output of the toString() implementations of the underlying resources instead of their getURL() implementations, which may throw an exception. Furthermore, logging the toString() output of resources aligns with the existing output for "allowed locations" in the same log message. Note that the toString() implementations could potentially also throw exceptions, but that is considered less likely. See gh-31623 Closes gh-31624 (cherry picked from commit 7d2ea7e)
|
Fixed via 86b8a70 |
sbrannen
changed the title
PathResourceResolver.getResource() never logs a warning for non-existent ServletContextResourcePathResourceResolver.getResource() does not log warning if Resource#getURL() throws exception
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Backport of gh-31623
The text was updated successfully, but these errors were encountered: