500 Internal Server Error Using ChromePHP
GuardianMajor opened this issue · 8 comments
I just loaded ChromePhp.php alongside a project I was hoping to test and it immediately results in an internal server error. Remove the include line to this file and everything runs fine without error.
I have no idea what's causing it as there is little to go on, any ideas what is going on?
Same problem here!
I have a feeling this project is dead and not being maintained, there is no activity on it and no responses from the developer. Shame, it was a nice idea.
Yea it really was :/
Chrome logger isn't dead. It sounds like this issue is specific to the PHP implementation though. The browser extension is not capable of altering the server side response codes of pages so I would guess this is PHP or Apache that is erroring. I think the ticket belongs here:
https://github.com/ccampbell/chromephp/issues
Without any more info though there is nothing I can do to help you. You will also see that the chromephp library itself never returns a 500:
https://github.com/ccampbell/chromephp/blob/c3c297615d48ae5b2a86a82311152d1ed095fcef/ChromePhp.php
Well what information do you need? I mean there is nothing really there to give. The fact is that you include the ChromePhp.php you get a 403 error and if you actually make a call to it inside the code, you get 500, that's it. What else do you need? Yes it seems that chromephp IS indeed causing the error because without its include or the call, nothing breaks, it doesn't have to return the error in the code to be causing it. If you think it needs to be put under the chromephp issues instead of here, then I am ok with you moving it but I can assure that nothing on our PHP or Apache is causing this unless its making a weird call or something that is breaking.
I just dropped mine into a file and didn't get an error. Logged out the information it was supposed to as it should.
@jcrben wish that was the case here but its not and I am not the only one facing the issue. Wish there was an internal logging system that would be able to shed light on when things go wrong as to what call caused it.
Looks like the issue has something to do with the size of the object being debugged. For me, small objects work and large objects fail. Is there some header size limit we need to be aware of or account for?