[Bug]: `A2A-Version` sent as a request parameter is ignored (spec §3.6.1), so a v1.0 request is treated as 0.3
Maintainer antworten meist innerhalb von 2 Tagen
@rohityan arbeitet bereits daran.
Seit 16.10.2026.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
What happened?
Summary
The server only reads A2A-Version from the request header. A client that sends the version as a request parameter, which the specification allows, is treated as a 0.3 client and gets VersionNotSupportedError for a valid v1.0 request.
Section 3.6.1 ("Client Responsibilities") of the v1.0.0 specification says: "Clients MAY provide the A2A-Version as a request parameter instead of a header." Its example is GET /tasks/task-123?A2A-Version=1.0. Section 3.6.2 then requires the agent to process the request using the semantics of the requested version.
DefaultServerCallContextBuilder.build() copies only request.headers into state['headers'] (src/a2a/server/routes/common.py:115), and validate_version reads only that dict (src/a2a/utils/version_validator.py:68). The query string is never consulted, so the request falls through to the empty-header default of 0.3.
Reproduce
pip install "a2a-sdk[http-server]==1.2.2" httpx, then run:
import asyncio
import httpx
from starlette.applications import Starlette
from a2a.server.agent_execution import AgentExecutor
from a2a.server.request_handlers import DefaultRequestHandler
from a2a.server.routes import create_jsonrpc_routes, create_rest_routes
from a2a.server.tasks import InMemoryTaskStore
from a2a.types import AgentCapabilities, AgentCard, AgentInterface
class Noop(AgentExecutor):
async def execute(self, context, event_queue): ...
async def cancel(self, context, event_queue): ...
card = AgentCard(
name="probe", description="probe", version="0.0.1",
capabilities=AgentCapabilities(),
supported_interfaces=[AgentInterface(
url="http://test/rpc", protocol_binding="JSONRPC", protocol_version="1.0")],
)
handler = DefaultRequestHandler(
agent_executor=Noop(), task_store=InMemoryTaskStore(), agent_card=card)
app = Starlette(routes=[*create_jsonrpc_routes(handler, "/rpc"),
*create_rest_routes(handler)])
RPC = {"jsonrpc": "2.0", "id": 1, "method": "GetTask", "params": {"id": "task-123"}}
HDR = {"A2A-Version": "1.0"}
async def main():
async with httpx.AsyncClient(transport=httpx.ASGITransport(app=app),
base_url="http://test") as c:
for label, resp in [
("JSON-RPC header ", await c.post("/rpc", json=RPC, headers=HDR)),
("JSON-RPC ?A2A-Version", await c.post("/rpc?A2A-Version=1.0", json=RPC)),
("HTTP+JSON header ", await c.get("/tasks/task-123", headers=HDR)),
("HTTP+JSON ?A2A-Version", await c.get("/tasks/task-123?A2A-Version=1.0")),
]:
body = resp.json()
err = body.get("error", body)
print(f"{label} -> HTTP {resp.status_code} {err.get('code')} {err.get('message')}")
asyncio.run(main())
Actual (identical on main at e86695c, and with enable_v0_3_compat=True):
JSON-RPC header -> HTTP 200 -32001 Task not found
JSON-RPC ?A2A-Version -> HTTP 200 -32009 A2A version '0.3' is not supported by this handler. Expected version '1.0'.
HTTP+JSON header -> HTTP 404 404 Task not found
HTTP+JSON ?A2A-Version -> HTTP 400 400 A2A version '0.3' is not supported by this handler. Expected version '1.0'.
Expected: the two ?A2A-Version=1.0 requests behave like the header requests and return Task not found.
On JSON-RPC the failure is quiet: an HTTP 200 carrying -32009. A client that checks the status code and then reads an SSE stream sees an empty stream, which looks like an agent with nothing to say.
Suggested fix
When the header is absent, fall back to the A2A-Version request parameter in DefaultServerCallContextBuilder.build(). That way every transport and validate_version see the same value. The spec does not say which wins when both are present; letting the header win seems the least surprising.
A smaller related improvement: when the client sent no version at all, say so in the error. Today the message reads "A2A version '0.3' is not supported", which suggests the client sent 0.3. Something like "no A2A-Version header or parameter; defaulted to 0.3, which this handler does not support" would point straight at the cause.
Relevant log output
Version mismatch: actual='0.3', expected='1.0'
Code of Conduct
- I agree to follow this project's Code of Conduct
- Vorherrschende Sprache
- Python
- Sterne
- 2.2k
- Forks
- 511
- Ø Merge
- 3 T. 7 Std.
- Gemergte PRs (30 T.)
- 46
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus a2aproject/a2a-python
-
[Bug]: REST task/request id sanitizationEvtl. vergeben @Linux2010 hat das vor 111 Tagen übernommen. Offenmaintainers-only
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
a2aproject/a2a-python#805 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 2 Tagen
-
[Bug]: Closing one client from a ClientFactory closes the shared httpx client for every other clientEvtl. vergeben @rohityan hat das heute übernommen. Offen
a2aproject/a2a-python#1349 · 2 zugewiesene Personen ·
Maintainer antworten meist innerhalb von 2 Tagen
-
[Bug]: A2A exceptions lost their structured __repr__ after the client error refactor (#761)Evtl. vergeben @rohityan hat das heute übernommen. Offen
a2aproject/a2a-python#1347 · 2 zugewiesene Personen ·
Maintainer antworten meist innerhalb von 2 Tagen
-
[Bug]: Client transports reject responses with unrecognized fields (spec 5.7)Evtl. vergeben @rohityan hat das vor 2 Tagen übernommen. Offen
a2aproject/a2a-python#1341 · 1 Kommentar · 2 zugewiesene Personen ·
Maintainer antworten meist innerhalb von 2 Tagen
-
DefaultRequestHandler (v2) ignores queue_manager, so the per-task event queue bound (1,024) cannot be configuredEvtl. vergeben @ishymko hat das vor 2 Tagen übernommen. Offencomponent: server status: needs review
a2aproject/a2a-python#1339 · 2 Kommentare · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 2 Tagen
Alle Issues in a2aproject/a2a-python
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 77/100
lidofinance/diffyscan#239 ·
Maintainer antworten meist innerhalb von 1 Tag
-
docs: the dev-setup table and AGENTS.md name the reviewed_by guard that CI's Changelog job runsOffenarea: tools documentation good first issue ready for a contributor
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
eyalgolan/statecraft-israel#873 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
GET rooms API returns 500 due to nonexistent Room.is_active attributeEvtl. vergeben @Mars-60 hat das heute übernommen. Offenbug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 5 Tagen
-
Harmony OPeNDAP SubSetter (HOSS) Geographic production rssmif16d 7 XYZ_PROV
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
nasa/harmony-autotester#341 ·