Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.4.0
Request #15240 Add ability to set content headers for new objects created via streams
Submitted: 2008-12-05 04:23 UTC
From: gauthierm Assigned: schmidt
Status: Closed Package: Services_Amazon_S3 (version CVS)
PHP Version: Irrelevant OS: Irrelevant
Roadmaps: (Not assigned)    
Subscription  


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 : 44 - 30 = ?

 
 [2008-12-05 04:23 UTC] gauthierm (Michael Gauthier)
Description: ------------ It would be useful to be able to set the content-type, content-disposition and content-encoding values for objects created via the stream wrapper. Currently all files created with the stream wrapper are set to binary/octet-stream. The attached patch adds the ability to set the content header values through the stream wrapper register or via a stream context.

Comments

 [2008-12-27 05:41 UTC] doconnor (Daniel O'Connor)
Changes look good to me
 [2009-01-15 18:00 UTC] schmidt (Christian Schmidt)
I made Content-Disposition and Content-Encoding be specified using a header array instead, for consistency with $object->httpHeaders vs. $object->contentType: http://news.php.net/php.pear.cvs/54909 Feedback on whether it works as expected would be appreciated :-)