struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "k918912 (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WW-5021) Serve static resources from different namespace
Date Fri, 22 Feb 2019 12:14:00 GMT

    [ https://issues.apache.org/jira/browse/WW-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775072#comment-16775072
] 

k918912 commented on WW-5021:
-----------------------------

@[~yasser.zamani]
{quote}So no, it doesn't resolve *all* static resources to /struts, but only the root application's
Struts resolve it's static resources to that and it is what logically anticipated.{quote}
Yes, I know. But I can't route /struts to my application for policy reasons. I know there
are ways around this (the first one would be the proper usage of not deploying the application
under root), but in my case I can't use that. I just thought that making this configurable
would be something that others might also be interested in, if this would only be specific
to my use case I wouldn't have created a bug report here.
@[~aleksandr-m]
{quote}Out of curiosity: I wonder, how do you found out of this if everything is working?{quote}
Because my application tried to load /struts/domTT.js and obviously my server was throwing
404 for that.

> Serve static resources from different namespace
> -----------------------------------------------
>
>                 Key: WW-5021
>                 URL: https://issues.apache.org/jira/browse/WW-5021
>             Project: Struts 2
>          Issue Type: Task
>    Affects Versions: 2.5.20
>            Reporter: k918912
>            Assignee: Lukasz Lenart
>            Priority: Major
>             Fix For: 2.6
>
>
> Is it somehow possible to serve the static Struts files from a different path?
> Currently domTT.js is loaded via /struts, but in my environment I would like to serve
it via /test/struts for example. Is there any configuration I'm missing or is this currently
not possible?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message