-
Notifications
You must be signed in to change notification settings - Fork 380
Open
Description
Describe the bug
Auth challenge for hitting / gives two WWW-Authenticate response headers. This is not functionally breaking, but it's possible for clients to misbehave with a plurality of this response header.
This is only affecting the feature/2.0beta-remote branch. Remote MCP server code is not in the main branch yet.
Expected behavior
Should only return a single challenge header
Actual behavior
WWW-Authenticate: Bearer realm="localhost:1031", resource_metadata="http://localhost:1031/.well-known/oauth-protected-resource"
WWW-Authenticate: Bearer
Reproduction Steps
curl -v -X POST http://localhost:1031/ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{ "jsonr
pc": "2.0", "id": "test123", "method": "tools/list", "params": {} }'
Environment
All environments
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Not Started