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
Then this base resource cannot serve content as the AliasCheck that come from the existing ServletContextHandler are not aware of this new Base Resource.
Now a user will have to add an additional AliasCheck for this new Base Resource.
Jetty version(s)
Jetty 12.0.7
Enhancement Description
If a user adds a DefaultServlet with a custom Base Resource, like this ...
Then this base resource cannot serve content as the
AliasCheck
that come from the existingServletContextHandler
are not aware of this new Base Resource.Now a user will have to add an additional AliasCheck for this new Base Resource.
This is particularly difficult to do when using dynamic servlet registration techniques, or with the servlet descriptor (
WEB-INF/web.xml
)I propose that the
DefaultServlet
itself auto-add theAllowedResourceAliasChecker
for any custom Base Resource that it is told to use.The text was updated successfully, but these errors were encountered: