Bug #4346 Updated: Suggestion for error trap in imagecreatefromjpeg

ID: 4346 Updated by: derick@php.net Reported By: leon@leonatkinson.com -Status: Open +Status: Bogus Bug Type: Feature/Change Request Operating System: all PHP Version: 4.1.2 New Comment: Not our problem, but a GD one. Derick Previous Comments: ------------------------------------------------------------------------ [2002-03-22 18:58:05] leon@leonatkinson.com My suggested functionality definitely works for GIF. I'm willing to assume it work the same with JPEG, PNG, etc...since they are all using GD, and because I'm too lazy to go recompile. :) ------------------------------------------------------------------------ [2002-02-24 07:16:13] sander@php.net Any change on this behaviour? ------------------------------------------------------------------------ [2000-05-07 16:29:03] leon@leonatkinson.com Here's a fun bug. I have a script that loads a JPEG with imagecreatefromjpeg and then sends it directly to the browser. No error from PHP, and it really was returning a resource, but when I called imagejpeg, it complained about an invalid resource. It took me about 15 minutes to realize that while the image was there, it had been corrupted by being transfered in ftp's ASCII mode. I don't know how practical it is because I haven't looked at the code, but it would be nice for imagecreatefromjpeg to return an error when the JPEG is corrupt. Likewise with the rest of the imagecreatefrom_ family. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=4346&edit=1