Edit report at https://bugs.php.net/bug.php?id=42445&edit=1

 ID:               42445
 Updated by:       php-bugs@lists.php.net
 Reported by:      jerome at rainstormconsulting dot com
 Summary:          fopen url wrapper doesn't handle chunked encoding
-Status:           Feedback
+Status:           No Feedback
 Type:             Feature/Change Request
 Package:          *General Issues
 Operating System: Any
 PHP Version:      5.2.3

 New Comment:

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.


Previous Comments:
------------------------------------------------------------------------
[2010-08-08 16:04:07] paj...@php.net

Please try using this snapshot:

  http://snaps.php.net/php5.3-latest.tar.gz
 
For Windows:

  http://windows.php.net/snapshots/



------------------------------------------------------------------------
[2010-08-08 15:52:17] artnorm at gmail dot com

This problem might be solved today. When I read it right on "HTTP context 
options" <http://www.php.net/manual/en/context.http.php>, chunked transfer 
should now be supported.

------------------------------------------------------------------------
[2007-08-27 14:46:13] jerome at rainstormconsulting dot com

Description:
------------
Opening a URL via fopen()/fread() does not work properly if Transfer-
Encoding: chunked is used

Reproduce code:
---------------
<?php
$fp = 
fopen('http://www.bluestatecoffee.com/blog/topics/blue-state-coffee-news/feed/rss2',
 'r');
$data = fread($fp, 45);
print htmlentities($data);

Expected result:
----------------
<?xml version="1.0" encoding="UTF-8"?>

Actual result:
--------------
29d0 <?xml version="1.0" encoding="UTF-8"?>


------------------------------------------------------------------------



-- 
Edit this bug report at https://bugs.php.net/bug.php?id=42445&edit=1

Reply via email to