#42911 [Com]: CURLOPT_ENCODING doesn't seem to support 'gzip'
| From: | daniel at haxx dot se | Date: | Wed, 10 Oct 2007 21:52:29 +0000 |
| Subject: | #42911 [Com]: CURLOPT_ENCODING doesn't seem to support 'gzip' | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-118373@lists.php.net to get a copy of this message | ||
ID: 42911
Comment by: daniel at haxx dot se
Reported By: dmceo415 at yahoo dot com
Status: Open
Bug Type: cURL related
Operating System: Windows XP
PHP Version: 4.4.7
New Comment:
It seems you're using a very old libcurl version... That text was
modified in 7.10.5 - which is well over 4 years old!
Previous Comments:
------------------------------------------------------------------------
[2007-10-10 13:49:48] dmceo415 at yahoo dot com
(changing my email address)
------------------------------------------------------------------------
[2007-10-10 03:21:35] dmceo415 at yahoo dot com
Description:
------------
The manual has this to say about CURLOPT_ENCODING:
'The contents of the "Accept-Encoding: " header. This enables decoding
of the response. Supported encodings are "identity", "deflate", and
"gzip". If an empty string, "", is set, a header containing all
supported encoding types is sent.'
However, when I use curl_setopt($ch, CURLOPT_ENCODING, 'gzip') in a
script, CURLOPT_VERBOSE tells me:
* Unrecognized content encoding type. libcurl understands 'identity'
and 'deflate' content encodings.
So, is the manual wrong, or is there a bug with respect to the 'gzip'
encoding?
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=42911&edit=1