You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, our static files api directly depends on Jetty's resource handler. It's a bit painful, because this implementation is relatively complex itself (because it works directly on Jetty's API) and it's one of the main blockers before exploring the possibility to use other http servers.
Requirements
The new implementation should:
Be fully compatible with current static API
Cover security related concerns to filter out malicious requests
Do not depend on Jetty and Jakarta EE servlet's API
The text was updated successfully, but these errors were encountered:
Context
Currently, our static files api directly depends on Jetty's resource handler. It's a bit painful, because this implementation is relatively complex itself (because it works directly on Jetty's API) and it's one of the main blockers before exploring the possibility to use other http servers.
Requirements
The new implementation should:
The text was updated successfully, but these errors were encountered: