[jboss-jira] [JBoss JIRA] (WFLY-3176) Certain file types are filtered out and excluded upon deployment

[Jason Kim (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Kim updated WFLY-3176:
----------------------------

    Description: 
In Wildfly 8.0.0, it was possible to deploy a web application with *.less files as well as other custom extensions, but with the latest build (Build #1041), when I  try to deploy an html page that references *.less files, the *.less files are unavailable and I get a 404 error. 

The same site along with the references to the *.less files worked on 8.0.0 FInal. I tried with other file types, just making up extensions, and Wildfly would not serve the files, instead it would return aa 404 when trying to access them.

  was:
In Wildfly 8.0.0, it was possible to deploy a web application with *.less files as well as other custom extensions, but with the latest build (Build #1041), when I  try to deploy an html page that references *.less files, the *.less files are unavailable and I get a 404 error. 

The same site worked on 8.0.0 FInal.


    
> Certain file types are filtered out and excluded upon deployment
> ----------------------------------------------------------------
>
>                 Key: WFLY-3176
>                 URL: https://issues.jboss.org/browse/WFLY-3176
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: Windows 7 x64
>            Reporter: Jason Kim
>
> In Wildfly 8.0.0, it was possible to deploy a web application with *.less files as well as other custom extensions, but with the latest build (Build #1041), when I  try to deploy an html page that references *.less files, the *.less files are unavailable and I get a 404 error. 
> The same site along with the references to the *.less files worked on 8.0.0 FInal. I tried with other file types, just making up extensions, and Wildfly would not serve the files, instead it would return aa 404 when trying to access them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira