ChromePhp not compatible with www.pagodabox.com

[dhollenbeck]

I have experienced the following problems with ChromePhp and www.pagodabox.com:

1. As the page loads in the browser I see ChromePhp messages being written to console. However, immediately after they are written they disappear as if something is clearing the console. The only way to see the console messages is to enable "Preserve log upon navigation" in Chrome. Once I do this I am able to see the log messages.
2. When logging PHP objects to the console the console records don't always expand in the console when you click on them. I have not been able to isolate the conditions that cause this yet, but it happens frequent enough.
3. Pagodabox has the apache instance configured to only accept http RESPONSE headers of size ~12K. Any headers greater than 12K will cause the apache service to just stop (ie sends no response including no headers to the browser). This is not a ChromePhp problem other than ChromePhp writes all of the data to a single header and does a number of encodings on the data that your application can quickly exceed the 12K http header limit.

I have been using ChromePhp for around six months and absolutely love it. I have only experienced these problems on www.pagodabox.com. I have not had any of these problems on other apache instances (XAMPP and rackspace).

However, I have moved on to FirePHP4Chrome and FirePHP which do not have any of these issues. The FirePHPChrome extension appears to write its data to the Chrome console must later in the process than ChromePhp does as it's console messages don't have this problem and show up after ChromePhp messages do. FirePHP also sends it data using more than one http header. It also uses a different encoding method that consumes less header space.

I would be happy to setup a test case on Pagodabox if helps. Thank you very much.

Thanks, Dan

[hakre]

Is your request perhaps using a redirect (compare #39)? To find out please provide the whole HTTP request and response header communication.