René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Support for separate registration and published endpoint paths in WebMvcSseServerTransportProvider","articleBody":"Please do a quick search on GitHub issues first, the feature you are about to request might have already been requested.\n\n**Expected Behavior**\nWebMvcSseServerTransportProvider should support separate configuration for registration paths and published paths. This would allow proper operation in environments with context paths or global URL prefixes.  Example usage:\n// Registration path: /message (for server routing)\n// Published path: /api/v1/message (what clients see/use)\nvar transportProvider = new WebMvcSseServerTransportProvider(\n    objectMapper, \n    \"/message\",             // Server registration path\n    \"/api/v1/message\",      // Path sent to clients\n    \"/sse\"\n);\nWith this enhancement, the server would register handlers at the bare paths, but communicate the full paths to clients through the SSE connection.\n\n**Current Behavior**\n\n When using WebMvcSseServerTransportProvider in environments with servlet context paths or other global URL prefixes (like Spring Boot's spring.mvc.servlet.path), there's a mismatch between:  \n\n1. The path where handlers are registered with Spring's RouterFunction (e.g., /message)\n2. The full path that needs to be communicated to clients (e.g., /app/message when the context path is /app)\n\nCurrently, WebMvcSseServerTransportProvider uses the same path for both registration and client communication, which doesn't work correctly in environments with context paths.\n**Context**\n\nI'm deploying an MCP server in a Spring Boot application with a servlet context path configured via spring.mvc.servlet.path. When registering message endpoints with Spring's RouterFunction, I need to use paths without the context prefix, but when communicating these endpoints to clients, I need to include the full path with context prefix.  I've considered workarounds like:  \n1. Using a reverse proxy to handle path translation (adds complexity)\n2. Manually modifying paths in client code (error-prone)\n3. Implementing a custom transport provider (duplicates existing code)\nA simple solution would be to enhance WebMvcSseServerTransportProvider to support separate configuration for registration and published paths, which would resolve this issue cleanly.\n","author":{"url":"https://github.com/minguncle","@type":"Person","name":"minguncle"},"datePublished":"2025-03-27T07:08:41.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/79/java-sdk/issues/79"}