Follow-ups to #1610: de-draft 2026-07-28 terminology, renumber error codes, ProtocolVersion floor (#1671)
This commit is contained in:
parent
90c853103d
commit
d6b1615988
1 changed files with 785 additions and 898 deletions
|
|
@ -65,8 +65,11 @@ public class ClientConformanceTests
|
|||
// HTTP Standardization (SEP-2243)
|
||||
[Theory(Skip = "SEP-2243 conformance scenarios not available (requires conformance package >= 0.2.0).", SkipUnless = nameof(HasSep2243Scenarios))]
|
||||
[InlineData("http-standard-headers")]
|
||||
[InlineData("http-custom-headers")]
|
||||
[InlineData("http-invalid-tool-headers")]
|
||||
// Commented out: the upstream scenario annotates a "number"-typed parameter with x-mcp-header,
|
||||
// which SEP-2243 forbids, so the client rejects the tool and sends no Mcp-Param-* headers,
|
||||
// failing every positive check. Re-enable once a conformant conformance package ships (#1655).
|
||||
// [InlineData("http-custom-headers")]
|
||||
public async Task RunConformanceTest_Sep2243(string scenario)
|
||||
{
|
||||
// Run the conformance test suite
|
||||
|
|
|
|||
Loading…
Reference in a new issue