Open Xploit3r opened 10 years ago
The issue above occurred while fuzzing IE6. I just tested with IE8 and the crash details are being reported to grinder server properly. I will recheck with IE6 to make sure that the issue is reproducible and also this problem occurs with other versions of Browser as well.
Hmm to be honest I'm not super sure why the data isn't being inserted. But have you noticed that the PHP code specifies "HTTP/1.0 200 OK", and you're getting "HTTP/1.1 200 OK"
Look closer: HTTP/1.0 vs HTTP/1.1? The version number is different.
Are you sure the function add_crash
was actually called?
do the logger actually log? i mean do you see the xml log files gets created in $logger_dir and grow i size?
because i believe that grinder dose not support IE6 or IE7 since node/browser/internetexplorer.rb dose not have the assembly code to patch any logging function (ie: parseFloat()) for IE6
On 11 June 2014 07:54, sinn3r notifications@github.com wrote:
Hmm to be honest I'm not super sure why the data isn't being inserted. But have you noticed that the PHP code specifies "HTTP/1.0 200 OK", and you're getting "HTTP/1.1 200 OK"
Look closer: HTTP/1.0 vs HTTP/1.1?
Are you sure the function add_crash was actually called?
— Reply to this email directly or view it on GitHub https://github.com/stephenfewer/grinder/issues/41#issuecomment-45699247.
Hi @Xploit3r, were you able to resolve this issue? like @mutfuzz mentioned, ie6/7 are not supported
On the grinder node: I got a crash for the browser.
Now, it posts the crash information to grinder server's status.php
I am able to see the crash data being sent in the HTTP POST request to the grinder server and also a 200OK response from it as shown below:
I have masked some information above.
Now, on grinder server: It does not report the crash on grinder server's web interface and does not show in crashes section either.
I checked the database tables, "crashes" using phpmyadmin on grinder server and no data specific to crash was inserted in the Database either.
The only statistics being updated on the grinder server are that the node is active and number of test cases tested per minute.
I checked the add_crash function defined in status.php and it should be inserting data in the crashes table when it receives the crash information from a grinder node
I am not sure why it is not inserting the data in the table.
Also, I can see that the grinder server responds with a 200OK response code.
And in status.php, if there was an error in processing the request, it would return 404 not found:
There should not be an issue in inserting data into the DB because the "nodes" table does get updated.
Help would be appreciated.
Thanks.