[ https://issues.jboss.org/browse/WFLY-5969?page=com.atlassian.jira.plugin.... ] Matthew Casperson commented on WFLY-5969: ----------------------------------------- Apologies - it does appear that context path has no effect. With or without context path, setting resolve-against-context-root does allow the delivery of static context when the default servlet is mapped to a subpath. However, I'm still a bit unclear on the intended functionality when resolve-against-context-root is mixed with something like this in web.xml: <servlet-mapping> <servlet-name>default</servlet-name> <url-pattern>/static/*</url-pattern> </servlet-mapping> i.e. this: https://github.com/mcasperson/wildfly-default-servlet-bug/blob/master/src... I would have expected the servlet mapping to allow only the static resources in the "static" directory to browsed and opened. With resolve-against-context-root set to true, browsing and downloading works for all directories, apparently ignoring the servlet-mapping. To demonstrate this I have deployed the war file generated from the sample app at https://github.com/mcasperson/wildfly-default-servlet-bug deployed to Wildfly 10 Final in Openshift at http://wildflybug1-kuna.rhcloud.com/wildfly-default-servlet-bug/. You'll note that http://wildflybug1-kuna.rhcloud.com/wildfly-default-servlet-bug/static2 can be browsed (ignore the fact that the response is plain text, I think that is an Openshift issue, as it is a valid HTML page when you run this locally), and http://wildflybug1-kuna.rhcloud.com/wildfly-default-servlet-bug/static2/d... can be downloaded, despite the default servlet being mapped only to the "static" directory. -- This message was sent by Atlassian JIRA (v6.4.11#64026)