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
The deployer tries to set a default context path when it deploys a webapp. In the case of ee9, the webapp will be an instanced of the nested/ContextHandler, which is a Supplier<ContextHandler> ie a supplier of core ContextHandler. The deployer gets the core ContextHandler and calls setContextPath(String) on it. Unfortunately, it is only in the nested/ContextHandler.setContextPath(String) method (which is not called) where we set up the _contextPathEncoded. It is the _contextPathEncoded that the Request uses. Thus, it appears as if the webapp is deployed correctly at the default context path, but any code that uses Request.getContextPath() will return null. We see this with the tck form security tests, where the redirect to the /login.jsp page is missing the _contextPathEncoded prefix.
The text was updated successfully, but these errors were encountered:
The deployer tries to set a default context path when it deploys a webapp. In the case of
ee9
, the webapp will be an instanced of thenested/ContextHandler
, which is aSupplier<ContextHandler>
ie a supplier of coreContextHandler
. The deployer gets the coreContextHandler
and callssetContextPath(String)
on it. Unfortunately, it is only in thenested/ContextHandler.setContextPath(String)
method (which is not called) where we set up the_contextPathEncoded
. It is the_contextPathEncoded
that theRequest
uses. Thus, it appears as if the webapp is deployed correctly at the default context path, but any code that usesRequest.getContextPath()
will return null. We see this with the tck form security tests, where the redirect to the/login.jsp
page is missing the_contextPathEncoded
prefix.The text was updated successfully, but these errors were encountered: