0 Replies Latest reply on Sep 1, 2016 9:51 AM by Tory Anderson

    Wildfly contexts for mixed standalone apps fronted by nginx

    Tory Anderson Newbie

      I have Wildfly 10.0.0 fronted by nginx, which reverse-proxies to various localhost:8080 places for wildfly to catch. Some of my apps are hit with a browser using example.com/app-name and everything works fine. However, other programs are to be hit with their own url, example2.com. In these cases, the apps are broken because all internal asset (css, js) requests are still being written as example2.com/app-name/asset when the asset is really available at example2.com/asset. I suppose a single app could be fixed by running at context "/", but in this shared environment, what is the solution?




      Cross posted before I found the Wildfly forum.