Note that there are some explanatory texts on larger screens.

plurals
  1. PONo reply when using flush(), session cookies and long execution time
    primarykey
    data
    text
    <p>I could reduce my problem to the following script I put on my server:</p> <pre><code>&lt;?php session_start(); header('Content-type: text/plain', TRUE); flush(); sleep(300);?&gt; </code></pre> <p>When I connect to this script using:</p> <pre><code>GET /test.php HTTP/1.1 Host: localhost </code></pre> <p>I get the header back right away as expected:</p> <pre><code>HTTP/1.1 200 OK Date: Sat, 03 Nov 2012 20:15:53 GMT Server: Apache/2.2.22 (Fedora) X-Powered-By: PHP/5.3.17 Set-Cookie: ZDEDebuggerPresent=php,phtml,php3; path=/ Set-Cookie: PHPSESSID=m7bmvblakkil96rqjq7j8f0f42; path=/ Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Connection: close Transfer-Encoding: chunked Content-Type: text/plain; charset=UTF-8 </code></pre> <p>If I then kill the connection and reconnect using:</p> <pre><code>GET /proxy/test.php HTTP/1.1 Host: localhost Cookie: PHPSESSID=knkeaq2ao0cllpcci0rnassqj4 </code></pre> <p>I don't get any header back anymore until I restart my webserver. I would have expected to again retrieve the response header right away. I have really no idea why I get this behavior. Maybe it's some kind of a bug? Or I'm misunderstanding some behavior. It would be great if somebody could help me with this as I really don't have a clue what's going on.</p> <p>Ps: Im running Apache/2.2.22 with PHP 5.3.17 on fedora 17, but the server packages are out of the fedora 16 repos as I need zend debugger which does not work with the PHP coming with fedora 17.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload