Jani,

Do you refer to:

http://cvs.php.net/viewcvs.cgi/php4/main/rfc1867.c?rev=1.62&content-type=text/vnd.viewcvs-markup&sortby=date

Or something else? If you think that one may be important I will apply and
see if it changes anything.

The above doesn't seem to be in PHP 4.0.5 but the other important
revisions, e.g. 1.59 do appear to be.

Nick.




On 2 May 2001, Bug Database wrote:

> ID: 10582
> Updated by: sniper
> Reported By: [EMAIL PROTECTED]
> Old-Status: Open
> Status: Feedback
> Old-Bug Type: *General Issues
> Bug Type: HTTP related
> PHP Version: 4.0.5
> Assigned To: 
> Comments:
> 
> Could you please try the latest CVS. There has been
> some fixes on this and I'm not sure if they maded to 4.0.5.
> 
> --Jani
> 
> 
> Previous Comments:
> ---------------------------------------------------------------------------
> 
> [2001-05-01 12:35:27] [EMAIL PROTECTED]
> I'm getting the following error message very occasionally (once daily) on a server 
>with approximately 1000 file uploads.
> 
> httpd: PHP Warning:  File Upload Error - No Mime boundary found after start of file 
>header in Unknown on line 0
> httpd: PHP Warning:  Cannot send session cache limiter - headers already sent 
>(output started at ]Q:40) in /web/script.php on line 12
> 
> This is co-inciding with an httpd process going crazy and using up all available CPU 
>and memory and bringing the machine down. I suspect there's a problem with the file 
>uploader client which is fine, but the crash is giving me major concerns.
> 
> This is proving hard to track down but the corruption in that second error message 
>leads me to think there may be something obvious to look at.
> 
> The script.php uses sessions, trans-sid and use_cookies 1
> 
> 
> Nick.
> 
> 
> 
> ---------------------------------------------------------------------------
> 
> 
> 
> ATTENTION! Do NOT reply to this email!
> To reply, use the web interface found at http://bugs.php.net/?id=10582&edit=2
> 
> 


--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to