Description: ------------ Hi, In HTTP/Request.php the response evaluation at line 742 say that Keep-Alive can only be used when (at option): - content-length is set - trasnfer-encoding is chunked I think there is another option to add : - HTTP response code is 204 I changed Request.php to this : $keepAlive = (isset($this->_response->_headers['content-length']) || (isset($this->_response->_headers['transfer-encoding']) && strtolower($this->_response->_headers['transfer-encoding']) == 'chunked') || $this->_response->_code == 204); and I can have only one socket created for my conversation. Test script: --------------- On a JAX-RS enabled java serveur (JBoss RESTEasy) when you do a DELETE /path query the server response is : DBG: Envoie de la requête DELETE sur http://localhost:8080/spotter-ws/api/traduction/services/traduction-synchro/132 DBG: Réponse à la requête: DBG: CODE HTTP 204 DBG: server = Apache-Coyote/1.1 DBG: x-powered-by = Servlet 2.5; JBoss-5.0/JBossWeb-2.1 DBG: date = Mon, 25 Jan 2010 11:42:14 GMT and no response body. Expected result: ---------------- The keep-alive connection should be kept alive. (with modified Request.php file) techno@spotter-dclnx:~$ netstat -t tcp -n | grep 8080 tcp 0 0 127.0.0.1:50476 127.0.0.1:8080 TIME_WAIT techno@spotter-dclnx:~$ Actual result: -------------- The keep-alive connection is closed. (with unmodified Request.php file) techno@spotter-dclnx:~$ netstat -t tcp -n | grep 8080 tcp 0 0 127.0.0.1:50469 127.0.0.1:8080 TIME_WAIT tcp 0 0 127.0.0.1:50470 127.0.0.1:8080 TIME_WAIT tcp 0 0 127.0.0.1:50468 127.0.0.1:8080 TIME_WAIT tcp 0 0 127.0.0.1:50467 127.0.0.1:8080 TIME_WAIT tcp 0 0 127.0.0.1:50471 127.0.0.1:8080 TIME_WAIT tcp 0 0 127.0.0.1:50465 127.0.0.1:8080 TIME_WAIT tcp 0 0 127.0.0.1:50472 127.0.0.1:8080 TIME_WAIT

Moving to HTTP_Request2

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.