0 Replies Latest reply on Aug 16, 2019 5:34 PM by worldsendless

    How to fix web context: Shared-server but exclusive url?

    worldsendless

      How do I get correct web-resource queries? My Wildfly is completely unaltered; just unpackaged and run. Here's the setup:

       

      ** Apache

          ServerName voyant.byu.edu
          ProxyPass / http://127.0.0.1:8080/voyant/
          ProxyPassReverse / http://127.0.0.1:8080/voyant/ 
      ### other stuff below
      
      

       

      ** File System

      Exploded jar file (in the directory voyant.war, which wildfly requires be named with that extension)

       

      wildfly-16.0.0.Final/
      ├── standalone
      │   ├── deployments
      │   │   └── voyant
      │   │       ├── voyant.war
      │   │       │   ├── app
      # etc

       

      Now, voyant.byu.edu routes correctly as a URL, loading the raw index contents. However, every other resource fails to be found because it is looking for the wrong URL, eg:

       

      http://voyant.byu.edu/voyant/resources/ext/6.2.0/charts-all.css

       

      It has a redundant layer voyant.byu.edu/voyant; if the /voyant were gone, it would be great. The resource is actually found here:

       

      http://voyant.byu.edu/resources/ext/6.2.0/charts-all.css

       

      Now, renaming things doesn't help; it's always <myapp>.myserver.com/<myapp>, which works fine if I'm running it at localhost:8080/<myapp>/<resource-path>, but fails given the reverse proxy on the shared server (which hosts multiple apps). What do I need to change to get this to just look for its resources in myapp.myserver.com/<resource-path>? Is it something in web.xml?