location parsing might incorrectly rely on the URL API [SPR-6332]

[spring-projects-issues]

Costin Leau opened SPR-6332 and commented

It's worth double checking whether the way resource locations are parsed throughout Spring rely on the URL API or not since the former can create false positives. Using the URI API is a better solution as it doesn't perform validation.

---

Issue Links:

• XML bean definition "import" directive doesn't work with custom resource loader [SPR-5762] #10432 XML bean definition "import" directive doesn't work with custom resource loader

[spring-projects-issues]

Costin Leau commented

After looking at both ResourceUtils#isUrl and ResourcePatternUtils#isUrl, I've came to the conclusion that these methods are in a correct way. Since in most cases, the location is opened as stream (and thus through an URL), transforming the validation into parsing would not provide any gains.