php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #5040 Support for persistent HTTP/1.0 connections
Submitted: 2000-06-14 22:25 UTC Modified: 2002-01-27 01:38 UTC
From: mnot at pobox dot com Assigned:
Status: Closed Package: Feature/Change Request
PHP Version: 4.0.0 Release OS:
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: mnot at pobox dot com
New email:
PHP Version: OS:

 

 [2000-06-14 22:25 UTC] mnot at pobox dot com
It would be great if PHP had an option which would buffer the response to the client, so that it could add a Content-Length header to enable persistent connections with HTTP/1.0 clients.

This could be done automagically, or there could just be an option to buffer the output of the script and make it available to a function which is called before sending to the client (so that things like compression could be done as well).

(I looked for a way to do this by importing a library, etc, but I don't see anything that would make it possible; if there is such a thing, a pointer would be much appreciated).

Note that IIS5 buffers ASP responses by default now; in 4, they could be turned on by setting a flag in the top of the script (forget what it is now)

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2000-07-08 21:43 UTC] mnot at pobox dot com
OK, I'm working on this in a library which can be appended. However, I really need access to HTTP headers that have already been set (specifically, Content-Type) by the PHP page.

Bug 5278 is exactly what I need.
 [2002-01-27 01:38 UTC] sterling@php.net
look at the output buffering functions.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sat Dec 21 12:01:31 2024 UTC