From issues-return-33171-archive-asf-public=cust-asf.ponee.io@struts.apache.org Fri Feb 22 13:11:04 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D61A3180648 for ; Fri, 22 Feb 2019 14:11:03 +0100 (CET) Received: (qmail 92253 invoked by uid 500); 22 Feb 2019 13:11:02 -0000 Mailing-List: contact issues-help@struts.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@struts.apache.org Delivered-To: mailing list issues@struts.apache.org Received: (qmail 92232 invoked by uid 99); 22 Feb 2019 13:11:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2019 13:11:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 5F138C2553 for ; Fri, 22 Feb 2019 13:11:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id iN73EpjscQGf for ; Fri, 22 Feb 2019 13:11:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id CBC4761393 for ; Fri, 22 Feb 2019 13:11:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 70B21E2799 for ; Fri, 22 Feb 2019 13:11:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 305C121311 for ; Fri, 22 Feb 2019 13:11:00 +0000 (UTC) Date: Fri, 22 Feb 2019 13:11:00 +0000 (UTC) From: "k918912 (JIRA)" To: issues@struts.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (WW-5021) Serve static resources from different namespace MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/WW-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775121#comment-16775121 ] k918912 commented on WW-5021: ----------------------------- @[~yasser.zamani] I think more explanation is needed. Root application doesn't mean that it's the main application. {quote}The demand of /struts/domTT.js means your root app is Struts, isn't it?! If it is, then it should work and 404 means another issue that should be investigated. If it isn't, then I think you should investigate who has generated the /struts/domTT.js (without context path) http request.{quote} I know, there is no bug in Struts, it is generating the correct result *but* my load balancer is only forwarding specific namespaces to my Struts application. So my load balancer gets a request to /test and routes it to the "root" Struts application, which in turn has actions mapped under /test, so everything works fine. Except for static resources, which I can't map to a namespace (which is what this whole ticket is about). So my application is generating /struts/domTT.js, but in my load balancer I can't (for company policy reasons) route /struts to my application. > 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)