Bug #8744 Updated: call to header() causes CGI error

ID: 8744 Updated by: php-bugs@lists.php.net Reported By: emily@crytech.com -Status: Feedback +Status: No Feedback Bug Type: IIS related Operating System: Windows 2000 PHP Version: 4.1.1 New Comment: No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". Previous Comments: ------------------------------------------------------------------------ [2002-03-25 09:11:00] sesser@php.net Guys try 4.1.2 I think this is just the 1000th duplicate of the header bug. ------------------------------------------------------------------------ [2002-03-25 02:57:10] develop@kiumars-ansari.de Hi to all, I have one Point to add. I use two copies of a WebSite on a Server running IIS (Test & Real). One of them dosn't have this Problem at all, but the Second one Produces this error. Both use the same Database Server. I compared the IIS Web Configuration, but both are the same! I can not find the error! Kiumars Ansari / Hamburg ------------------------------------------------------------------------ [2002-03-18 17:15:58] php@gustl.at I read your errors and found: FATAL: erealloc(): Unable to allocate 1043162510 bytes this seems to me like a MSSQL-PHP issue which comes along with the use of MSSQLs NTEXT and NVARCHAR Fields, after connecting to the MSSQL-database you must launch a SQL statement which limits the returning size fo this fields eg. 'SET TEXTSIZE 100000'. hope this helps Gustav Graf ------------------------------------------------------------------------ [2002-03-14 06:52:39] stain@NOSPAM_studenti.it i noticed various problem working on header() function. in the worst case i get out a segmentation fault on my linux 2.4.4 running apache 1.3.22 + php 4.1.1 i will post a new bug thread about it in few minutes... bye, stain ------------------------------------------------------------------------ [2002-03-12 15:41:15] sabram@NO-SPAM.telus.net Hi All, I also have this problem and it is definately related to MSSQL because I also used the same code with a MySQL database and the error doesn't exist. Thanks, Steve ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/8744 -- Edit this bug report at http://bugs.php.net/?id=8744&edit=1