markhoerth opened a new issue, #10846:
URL: https://github.com/apache/gravitino/issues/10846

   ### Version
   
   main branch
   
   ### Describe what's wrong
   
   ## What version of Gravitino are you using?
   
   main (commit 614302c, PR #10840)
   
   ## What happened?
   
   #10840 added root-level health aliases `/health`, `/health/live`, 
`/health/ready` that forward to `/api/health/*`. The aliases are documented as 
"for enterprise GTM standards that hardcode well-known root paths" but 
`/health.html` — one of the most commonly hardcoded GTM probe paths — returns 
404.
   
   ## Expected behavior
   
   `/health.html` returns HTTP 200 with the same aggregate JSON body as 
`/health` and `/api/health`. `.html` is not a sub-path of `/health`; it's a 
legacy web-server convention used as a sibling, common in enterprise GTM 
onboarding standards that predate K8s-style probe endpoints.
   
   ## Note on test gap
   
   This regression slipped through because `TestHealthAliasServlet` tests mock 
`getRequestDispatcher()`, which validates the servlet's path-rewriting logic 
but doesn't exercise Jetty's path-spec matching in 
`GravitinoServer.addServlet(...)`. The bug is one level up from what the unit 
test covers. Worth considering an integration test that boots the server and 
curls each GTM-relevant path.
   
   ### Error message and/or stacktrace
   
   ./gradlew clean assembleDistribution -x test
   ./distribution/gravitino-1.3.0-SNAPSHOT-bin/bin/gravitino.sh start
   curl -s -o /dev/null -w "%{http_code}\n" http://localhost:8090/health        
# 200 ✓
   curl -s -o /dev/null -w "%{http_code}\n" http://localhost:8090/health.html   
# 404 ✗
   curl -s -o /dev/null -w "%{http_code}\n" http://localhost:8090/api/health    
# 200 ✓
   
   ### How to reproduce
   
   ./gradlew clean assembleDistribution -x test
   ./distribution/gravitino-1.3.0-SNAPSHOT-bin/bin/gravitino.sh start
   
   ### Additional context
   
   _No response_


-- 
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