CodeIgniter Forums

Full Version: server error 500
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Well CI is shoving a slew of html data into my buffer (before I add my stuff to to it) and it is causing the server to go crazy and give a server 500 error. It was a bear to find this, but now that I know the problem, how do I solve it? I am using XMLHttp to do this communication but I am wondering if that is the problem? Is there some way I can view the output buffer before it goes out from the output command? 

Any ideas of what to do?
There is a problem in your .htaccess file check it
Thanks. I am trying to get Wireshark setup to decrypt my SSL so I can see what is wrong with the headers. I'll let you guys know if it is a CI bug.
It's not a CI bug that's for sure.
I agree with you! At some point the apache is going into an error state. I have wireshark on it trying to see what is the last thing that happens before it goes that way.
OK. Finally made some progress. I am debugging on the remote server with phpStorm. In index.php there is a line:

$system_path = 'system';

When I look at system (under the debugger) it is pointing at c:\xmapp\htdocs\sub_crud\system. Shouldn't this be pointing at a location on the remote server? a few lines down I see

$system_path = $_temp.DIRECTORY_SEPARATOR; which is c:\xampp\htdocs\sub_crud\system

a few lines below that I see that BASEPATH is getting defined as $system_path.

So the bottom line is that my code on the remote server is trying to use the system on my local hard drive. How do I fix this? 

I modified $system_path='\opt\bitnami\apache2\htdocs\sub_crud\system';

but now I get
PHP Code:
    if ( ! is_dir($system_path))
header('HTTP/1.1 503 Service Unavailable.'TRUE503);
'Your system folder path does not appear to be set correctly. Please open the following file and correct this: '.pathinfo(__FILE__PATHINFO_BASENAME);

Well, I think I might have found the problem. Seems that there was an Apache bug where "junk" was being written into stdout.

I am running Apache 2.4.33. I wonder if this was ever patched on my version? How can I determine if this is the actual problem?

This guys problem seems pretty much like mine.