Skip to content

Conversation

@ashakirin
Copy link
Contributor

fixes java mcp message endpoint error #103

@ashakirin ashakirin marked this pull request as ready for review April 14, 2025 15:12
@tzolov tzolov self-assigned this Apr 15, 2025
tzolov pushed a commit that referenced this pull request Apr 18, 2025
Improve endpoint URI handling by supporting both relative paths
and properly validated absolute URIs.

- Implement URI resolution in HttpClientSseClientTransport:
- Change baseUri field from String to URI type
- Add Utils.resolveUri method to handle both absolute and relative URIs
- Resolve relative URIs against the base URI
- Validate absolute URIs to ensure they match base URI's scheme, authority, and path
- Add parameterized tests for various URI resolution scenarios
- Add ByteBuddy dependency for HttpClient mocking and update Mockito

Signed-off-by: Christian Tzolov <christian.tzolov@broadcom.com>
@tzolov tzolov added this to the 0.10.0 milestone Apr 18, 2025
@tzolov tzolov added enhancement New feature or request area/client labels Apr 18, 2025
@tzolov
Copy link
Contributor

tzolov commented Apr 18, 2025

Thanks @ashakirin !

cherry-picked, edited, squashed, rebased and merged at 344f1b8

@tzolov tzolov closed this Apr 18, 2025
@CaelumF
Copy link

CaelumF commented May 12, 2025

Should the default sse endpoint not be ./sse instead of /sse ? when running with localhost/something/something in the basePath (multiple servers are intended to be reachable in the same program), the change from the latest dev snapshot is resolving to just localhost/sse @tzolov

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/client enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants