sbglasius commented on PR #15227:
URL: https://github.com/apache/grails-core/pull/15227#issuecomment-3554670820

   @jdaugherty here's what I did to test:
   
   Checked out https://github.com/Noirtam/grails-core/tree/issues_15132 and 
build according to INSTALL
   
   Added to `application.yml`
   ```
   ---
   server:
     servlet:
       context-path: /demo
   ```
   
   Created two controllers:
   ```
   package DemoApplication
   
   class TestAlphaController {
       
       def index() {
           redirect(controller: 'testBeta', action: 'index')
       }
   }
   ```
   and
   ```
   package DemoApplication
   
   class TestBetaController {
       
       def index() {
           render 'OK'
       }
   }
   ```
   
   First I ran the application with `./gradlew bootRun` and saw that it started 
on `http://localhost:8080/demo`, clicked on 
`http://localhost:8080/demo/testApha` and was redirected to `/demo/testBeta` 
and `OK` was rendered.
   
   Secondly I build `./gradlew war` and deployed that to a vanilla Tomcat 10, 
by placing the created warfile in `webapps/demo.war` and fired up tomcat.
   
   Again I did the same test, and everything worked
   
   Finally I stopped tomcat, removed `webapps/demo` and renamed `demo.war` to 
`test.war` (new context), and fired up tomcat.
   
   Now I hit `http://localhost:8080/test`, clicked on 
`http://localhost:8080/test/testApha` and was redirected to `/test/testBeta` 
and `OK` was rendered.
   
   For extra testing I build `./gradle bootJar` and ran that:
   
   ```
   java -jar build/libs/DemoApplication-0.1.jar    
   ```
   
   and secondly with a different context-path:
   ```
   java -Dserver.servlet.context-path=/test -jar 
build/libs/DemoApplication-0.1.jar 
   ```
   
   Also both worked as expected.
   
   My conclusion is, that the patch works as expected in all scenarios
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to