Header Response 200 and Content Type text/plain via Controller

[eluser]BrianDHall[/eluser]
Well that seems more or less reasonable - now just have to see what headers are really being obtained and sent to the browser and see where the disconnect is.

[eluser]shiftpoint[/eluser]
From livehttpheaders:


HTTP/1.x 200 OK
Date: Fri, 23 Oct 2009 18:59:19 GMT
Server: Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.9
X-Powered-By: PHP/5.2.9
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: ci_session=a:4:{s:10:"session_id";s:32:"2673af550ced8759fffc01a7d4d28402";s:10:"ip_address";s:12:"97.65.65.226";s:10:"user_agent";s:50:"Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+en-US;+rv";s:13:"last_activity";s:10:"1256324359";}bccc49f1f52d54d9cf8fe73637501713; expires=Fri, 23-Oct-2009 20:59:19 GMT; path=/
Content-Length: 360
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html

[eluser]shiftpoint[/eluser]
Could it something to do with the ci_session stuff?

[eluser]shiftpoint[/eluser]
Any ideas? I really need to get this fixed....

[eluser]BrianDHall[/eluser]
I think you might need a debugger to figure out the 'why', but to make it work try sticking a call directly to headers somewhere it shouldn't be, like in a core file - force it to send unnaturally. Maybe even hack part of the output class just to see if you can get it working whatsoever, then perhaps that will shed light on why it doesn't work the way it is supposed to.

[eluser]tomcode[/eluser]
If plain PHP works and CI not, I'd start from scratch :
1. install a CI on local and remote
2. add test Controller / view with the isolated core functionality
3. start debugging
4. add more until it breaks

[eluser]shiftpoint[/eluser]
I will do some debugging today and see if I can't figure it out. Any more ideas are always welcome :-)

[eluser]shiftpoint[/eluser]
Found something interesting. Check out the headers via localhost and production. Any idea what would cause the production ones to be different?

Localhost:

HTTP/1.x 200 OK
Content-Length: 22
Content-Type: text/plain charset=UTF-8
Server: Microsoft-IIS/7.5
X-Powered-By: PHP/5.2.10
Date: Wed, 28 Oct 2009 15:42:20 GMT
----------------------------------------------------------
Production:

HTTP/1.x 200 OK
Date: Wed, 28 Oct 2009 16:48:22 GMT
Server: Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.9
X-Powered-By: PHP/5.2.9
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: ci_session=a:4:{s:10:"session_id";s:32:"2c8590e1793f38f69b9d317fbf280ea6";s:10:"ip_address";s:12:"97.65.65.226";s:10:"user_agent";s:50:"Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+en-US;+rv";s:13:"last_activity";s:10:"1256748504";}6db8c562e41e27a320f8cf606d916f88; expires=Wed, 28-Oct-2009 18:48:24 GMT; path=/
Content-Length: 22
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html

[eluser]shiftpoint[/eluser]
I think it might have something to do with the "mod_header" apache module...

[eluser]Ricardo SDL[/eluser]
I'm running under linux/apache, and I couldn't set the proper content-type. I've ran this command "apache2 -l" and I didn't see this "mod_header". Any ideas of a soluiton?
Thanks!