Skip to content
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

Consider adding support for resolving base64 encoded resources #32539

Closed
vpavic opened this issue Mar 26, 2024 · 2 comments
Closed

Consider adding support for resolving base64 encoded resources #32539

vpavic opened this issue Mar 26, 2024 · 2 comments
Labels
status: declined A suggestion or change that we don't feel we should currently apply

Comments

@vpavic
Copy link
Contributor

vpavic commented Mar 26, 2024

Spring Boot recently added support for this in spring-projects/spring-boot#36033, however IMO this is something very useful generally (and not only in Spring Boot based applications) and especially when working in environments without a traditional filesystem that are common these days. As such it could potentially be considered as a candidate for inclusion in Framework's support for handling resources.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Mar 26, 2024
@quaff
Copy link
Contributor

quaff commented Mar 27, 2024

It looks like data URI

@snicoll
Copy link
Member

snicoll commented Apr 5, 2024

Thanks for the suggestion. We have discussed this with the Spring Boot team and they have more things they'd like to add around that feature. Adding it here only really makes sense if we support it by default and adding a default protocol resolver in the core framework can have side effects with regards to the prefix we choose.

All in all, we don't think it's the right time to consider including it here and this issue is no longer actionable. We can reconsider at a later time based on the community feedback.

@snicoll snicoll closed this as not planned Won't fix, can't repro, duplicate, stale Apr 5, 2024
@snicoll snicoll added status: declined A suggestion or change that we don't feel we should currently apply and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply
Projects
None yet
Development

No branches or pull requests

4 participants