No wildfire payload found

[saso]

I keep getting the following message. What could be wrong? What does
the response body mean?

Thank you


-------------------------------------------------------------


No wildfire payload found in 'Server URL' response. Check 'Response
Body' below for error messages.

Homepage URL: http://localhost/firephp/

Server URL: http://localhost/firephp/

Response Status: 200

Response Headers:
Date: Mon, 22 Aug 2011 09:15:46 GMT
Server: Apache/2.2.16 (Win32) mod_ssl/2.2.16 OpenSSL/0.9.8o
X-Powered-By: PHP/5.3.5 ZendServer
Keep-Alive: timeout=5, max=99
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html

Response Body:



x-wf-protocol-1: http://registry.pinf.org/cadorn.org/wildfire/@meta/protocol/component/0.1.0
x-wf-1-index: 1
x-wf-1-1-receiver: http://registry.pinf.org/cadorn.org/insight/@meta/receiver/insight/controller/0
x-wf-1-1-1-sender: http://localhost/firephp/?lib=cadorn.org/github/firephp-libs/packages/ins...@0.0.0master1106021548
x-wf-1-1-1-1: 74||{"action":"testClient","actionArgs":{"payload":
{"time":"1314004545397"}}}|

[Christoph Dorn]

saso 22 August, 2011 2:20 AM

I keep getting the following message. What could be wrong? What does
the response body mean?

The response body in this case is the data sent when the client connects to the server to fetch the logging data.

Based on this output you are testing the following URL:

  http://localhost/firephp/

The client reads the headers returned and makes a second call to the "Server URL":

  http://localhost/firephp/

The client sends some POST parameters with the second request which FirePHP intercepts, locates the logging data for the last request and sends this to the client.

The output shows that the response body does contain logging data which is what is expected.

So I am wondering if it is significant that there are extra newlines at the top of the response body. The client should be trimming these before parsing the response.

I just tested this (extra newlines) and it does seem to be the issue. I'll patch this for the next release.

In the meantime make sure you are including FirePHP as the very first thing in all your pages and that there are no spaces or newlines generated prior.

Thanks for reporting this bug!

Christoph