[
https://issues.jboss.org/browse/WFLY-4254?page=com.atlassian.jira.plugin....
]
Kris Iyer commented on WFLY-4254:
---------------------------------
The defects you refer to as being rejected earlier are against AS7.0, and 7.1.1 which had
known issues. This is also supported under AS 7.4 - EAP 6.3. The schema supports this as
part of web metadata, but not respected by the web container. I recommend that we do not
reject this based off AS7-3357 that was rejected 2 years ago, and then a fix comes up in
EAP 6.1.0.Alpha (7.2.0.Final). On a related note, supporting symbolic links is useful for
exploded content and scaling deployments in the cloud, where bind mounts are not always
easy to work with and automate and often times error prone.
Symbolic links within web applications do not work
--------------------------------------------------
Key: WFLY-4254
URL:
https://issues.jboss.org/browse/WFLY-4254
Project: WildFly
Issue Type: Feature Request
Components: Web (Undertow)
Affects Versions: 8.2.0.Final
Reporter: Kris Iyer
Assignee: Bartosz Baranowski
Symbolic Linking under exploded web-apps to files and/or directories outside the web-app
do not work.
Here is what I tried under an exploded war:
<jboss-web
xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd"
version="8.0">
<symbolic-linking-enabled>true</symbolic-linking-enabled>
</jboss-web>
Does not follow links and results in a 404.
HTTP/?.? 404 Not Found
Connection: keep-alive
X-Powered-By: Undertow/1
Server: WildFly/8
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)