Skip to content

Clarify CONTEXT_PATH servlet mapping behavior and path conflicts#3983

Closed
Copilot wants to merge 2 commits intoissue-3728-context-pathfrom
copilot/sub-pr-3978
Closed

Clarify CONTEXT_PATH servlet mapping behavior and path conflicts#3983
Copilot wants to merge 2 commits intoissue-3728-context-pathfrom
copilot/sub-pr-3978

Conversation

Copy link
Copy Markdown

Copilot AI commented Feb 11, 2026

The CONTEXT_PATH documentation was misleading—it showed /metrics becoming /print/metrics but didn't clarify that /print/* becomes /print/print/*, potentially confusing users about path conflicts.

Changes:

  • Explicitly document all servlet path transformations when CONTEXT_PATH is set
  • Add warning against using /print or /sec as CONTEXT_PATH values (results in double-prefixing)
  • Change examples from /print to /printservice to demonstrate non-conflicting usage

Example:
With CONTEXT_PATH=/print, all servlet mappings are prefixed:

  • /metrics/print/metrics
  • /print/*/print/print/* (likely unintended)
  • /sec/print/*/print/sec/print/* (likely unintended)

Use a non-conflicting path like /printservice instead.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

…avior

Co-authored-by: sbrunner <353872+sbrunner@users.noreply.github.com>
Copilot AI changed the title [WIP] Add CONTEXT_PATH support for sub-path deployments Clarify CONTEXT_PATH servlet mapping behavior and path conflicts Feb 11, 2026
Copilot AI requested a review from sbrunner February 11, 2026 09:06
@sbrunner sbrunner closed this Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants