php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #3464 imap_fetchstructure incompatible behavior
Submitted: 2000-02-12 03:22 UTC Modified: 2000-02-29 10:47 UTC
From: tho at nextlayer dot com Assigned:
Status: Closed Package: IMAP related
PHP Version: 3.0.14 OS: Solaris
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
21 + 15 = ?
Subscribe to this entry?

 
 [2000-02-12 03:22 UTC] tho at nextlayer dot com
imap.c 1.75 made an incompatible change to imap_add_body().
This is not mentioned in the CVS log or the Changelog.

Prior to PHP 3.0.14, one might say, e.g.:

$s = imap_fetchstructure($mbox, $msg);
if (!isset($s->encoding))
  echo "This is a friendly message.\n";
else echo "The body requires annoying MIME processing.\n";

As of 3.0.14, "encoding" is always set (even if zero,
i.e. ENC7BIT), "breaking" the above test.  Similar
code using the "type" property also fails.

In a perfect world, these properties would be set if and
only if Content-Type, Content-Transfer-Encoding were
explicitly present in the selected message.


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2000-02-29 10:47 UTC] hholzgra at cvs dot php dot net
re-fixed in imap.c 1.77
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Fri Mar 29 04:01:29 2024 UTC