From 746cc049d02c898667aa223bfb1374e0a5975d24 Mon Sep 17 00:00:00 2001 From: Benoit Chesneau Date: Fri, 3 Apr 2026 23:13:27 +0200 Subject: [PATCH] Skip HTTP 100 Continue test - invalid per RFC 7231 HTTP 100 Continue is an informational response that must be followed by a final response. Testing it as a final response is invalid HTTP. --- .../docker/asgi_framework_compat/tests/test_http_messages.py | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/tests/docker/asgi_framework_compat/tests/test_http_messages.py b/tests/docker/asgi_framework_compat/tests/test_http_messages.py index a549b2f9..7cc1fa18 100644 --- a/tests/docker/asgi_framework_compat/tests/test_http_messages.py +++ b/tests/docker/asgi_framework_compat/tests/test_http_messages.py @@ -73,11 +73,12 @@ class TestHttpResponseStatus: response = await http_client.get(f"/status/{code}") assert response.status_code == code + @pytest.mark.skip(reason="HTTP 100 Continue cannot be a final response per RFC 7231") async def test_status_100_continue(self, http_client): """Handle 100 status (may not be supported by all frameworks).""" - # Some frameworks may not support 100, so we just check it doesn't crash + # HTTP 100 Continue is an informational response that must be followed + # by a final response. Using it as a final response is invalid. response = await http_client.get("/status/100") - # 100 is special - some servers transform it assert response.status_code in (100, 200)