HTTP server: Persistent connection on HTTP/1.0 hangs, when using streaming response body
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 76/100
Línea de trabajo
Start at src/Io/StreamingServer.php around line 308 and reproduce the issue with the provided streaming ThroughStream example and curl --http1.0 request. Trace how an HTTP/1.0 response with an unknown body size handles Connection: keep-alive; done means the response is transmitted and the connection closes instead of hanging.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Assuming the response body is streaming and its size is unknown, when a request such as this is received:
GET / HTTP/1.0
Connection: keep-alive
ReactPHP produces a response without a Content-Length header, such as this:
HTTP/1.0 200 OK
Connection: keep-alive
<data>
and doesn't close the connection, which then just hangs until timeout, because for the client there is no way of telling, when the response data is finished transmitting.
Steps to reproduce:
$server = new React\Http\HttpServer(function () {
$stream = new ThroughStream();
Loop::futureTick(function () use ($stream) {
$stream->write("foo\n");
$stream->end();
});
return new Response(200, body: $stream);
});
$socket = new React\Socket\SocketServer("0.0.0.0:80");
$server->listen($socket);
curl -v --http1.0 -H "connection: keep-alive" localhost:80
Tested on v1.11.0 and 3.x-dev (4e1b4f369eea9428ac38b8851e113ce5ad47cbee).
Since it's HTTP/1.0, Transfer-Encoding: chunked cannot be used. I believe the only good way to handle this situation is to ignore the requested Connection: keep-alive and just close the connection after the response is transmitted. I think this should be a valid behavior - server is not required to strictly obey the keep-alive request header.
The relevant code is here: https://github.com/reactphp/http/blob/1.x/src/Io/StreamingServer.php#L308
- Lenguaje dominante
- PHP
- Estrellas
- 781
- Forks
- 166
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de reactphp/http
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
-
Roadmap to reactphp/http v3 Abiertomaintenance
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
-
new feature
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
-
help wanted new feature
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
-
new feature
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
Todos los issues de reactphp/http
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
getgrav/grav-plugin-api#45 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
RSS-Bridge/rss-bridge#5098 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
phingofficial/phing#2025 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
silverstripe/developer-docs#911 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100