Add Accept header for HTTP MCP backend session establishment #183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The safeinputs HTTP backend returns "Session not found" (404) because the gateway doesn't send the required
Acceptheader during session establishment.Changes
Accept: application/json, text/event-streamheader to HTTP MCP requestsinitializeHTTPSession(): Ensures proper content negotiation during session creationsendHTTPRequest(): Maintains consistency for all HTTP backend communicationContext
HTTP MCP backends like safeinputs require explicit content type negotiation to establish sessions. Without the Accept header, the backend cannot determine the response format, leading to session initialization failures.
This aligns with the safeinputs server's documented initialization flow, which captures the session ID from response headers for subsequent authenticated requests.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.