<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Thu, 20 Jun 2013 00:08:09 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Lukas Smith's Blog: One thumb up and two down (Zend_Http_Client)]]></title>
      <guid>http://www.phpdeveloper.org/news/10418</guid>
      <link>http://www.phpdeveloper.org/news/10418</link>
      <description><![CDATA[<p>
Coming back from some <a href="http://www.phpdeveloper.org/news/10381">previous comments</a> about the Zend_Http_Client in the Zend Framework, <i>Lukas Smith</i> admits that a <a href="http://framework.zend.com/manual/en/zend.http.client.adapters.html#zend.http.client.adapters.proxy">certain feature</a> has come in handy with their development, but another bug has come up that has gotten under his skin - a problem with the component's cookie handling.
</p>
<blockquote>
We ran into a really hard to find <a href="http://framework.zend.com/issues/browse/ZF-1850">bug in the cookie handling</a> of Zend_Http_Client, which has been filed as a bug back in August 2007 against version 1.0.1 (today we are at 1.5.2). More over this is a bug that other similar packages have <a href="http://pear.php.net/bugs/bug.php?id=1080">gotten over in 2004</a>.
</blockquote>
<p>
He had to use <a href="http://www.wireshark.org/">wireshark</a> to finally track down the culprit - a call to urlencode on the contents of the cookie before sending it. He also includes some code to overcome a problem he had with UTF-16 in one of his feeds (a custom function that takes in and returns a string translated correctly).
</p>]]></description>
      <pubDate>Mon, 16 Jun 2008 09:32:24 -0500</pubDate>
    </item>
  </channel>
</rss>
