<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Parsing PUT requests in PHP</title>
	<link>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Sun, 12 Oct 2008 23:35:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Ian</title>
		<link>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html#comment-20105</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Tue, 23 Sep 2008 16:07:08 +0000</pubDate>
		<guid>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html#comment-20105</guid>
		<description>Joe, working on a RESTful service as well, and this is the only way I could dig up to parse PUT requests (also works for DELETE if you ever need to send body for some odd reason).  One thing I've done that might make life a bit easier in some cases is to use JSON to chuck the data around, but you still end up having to do some goofy stuff to get the string sanitized so it can be properly json_encoded / decoded.

Separately, it gets even goofier when you need to make PUT requests in your code, as you need to stream the data into memory before you can curl it, as curl PUTs only accept files... definitely need some better native support for REST in php.</description>
		<content:encoded><![CDATA[<p>Joe, working on a RESTful service as well, and this is the only way I could dig up to parse PUT requests (also works for DELETE if you ever need to send body for some odd reason).  One thing I&#8217;ve done that might make life a bit easier in some cases is to use JSON to chuck the data around, but you still end up having to do some goofy stuff to get the string sanitized so it can be properly json_encoded / decoded.</p>
<p>Separately, it gets even goofier when you need to make PUT requests in your code, as you need to stream the data into memory before you can curl it, as curl PUTs only accept files&#8230; definitely need some better native support for REST in php.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tylermenezes</title>
		<link>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html#comment-20078</link>
		<dc:creator>tylermenezes</dc:creator>
		<pubDate>Thu, 05 Jun 2008 02:14:49 +0000</pubDate>
		<guid>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html#comment-20078</guid>
		<description>This is defiantly something that needs to be addressed in future versions of PHP. Works for me, though. Thanks!</description>
		<content:encoded><![CDATA[<p>This is defiantly something that needs to be addressed in future versions of PHP. Works for me, though. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joe</title>
		<link>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html#comment-20073</link>
		<dc:creator>joe</dc:creator>
		<pubDate>Wed, 21 May 2008 15:19:05 +0000</pubDate>
		<guid>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html#comment-20073</guid>
		<description>I did notice that PECL extension, but, alas, it also returns a string. I'd still have to use &lt;code&gt;parse_str()&lt;/code&gt; to import the data. Additionally, the method I've outlined doesn't require loading another module.</description>
		<content:encoded><![CDATA[<p>I did notice that PECL extension, but, alas, it also returns a string. I&#8217;d still have to use <code>parse_str()</code> to import the data. Additionally, the method I&#8217;ve outlined doesn&#8217;t require loading another module.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Gonzalez</title>
		<link>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html#comment-20072</link>
		<dc:creator>Robert Gonzalez</dc:creator>
		<pubDate>Wed, 21 May 2008 05:05:08 +0000</pubDate>
		<guid>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html#comment-20072</guid>
		<description>I think there is a PECL class that might do it. I found &lt;a href="http://us.php.net/manual/en/function.HttpRequest-getPutData.php" rel="nofollow"&gt;this in the PHP manual&lt;/a&gt;. Not sure if it will do what you need it to.</description>
		<content:encoded><![CDATA[<p>I think there is a PECL class that might do it. I found <a href="http://us.php.net/manual/en/function.HttpRequest-getPutData.php" rel="nofollow">this in the PHP manual</a>. Not sure if it will do what you need it to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joe</title>
		<link>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html#comment-20071</link>
		<dc:creator>joe</dc:creator>
		<pubDate>Mon, 19 May 2008 16:07:22 +0000</pubDate>
		<guid>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html#comment-20071</guid>
		<description>We're not. These aren't public services.</description>
		<content:encoded><![CDATA[<p>We&#8217;re not. These aren&#8217;t public services.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: keithelder</title>
		<link>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html#comment-20070</link>
		<dc:creator>keithelder</dc:creator>
		<pubDate>Sun, 18 May 2008 22:17:35 +0000</pubDate>
		<guid>http://www.joestump.net/2008/05/parsing-put-requests-in-php.html#comment-20070</guid>
		<description>Joe, I'm curious as to how you are securing these services to make sure requests are only coming from the places you think it is.</description>
		<content:encoded><![CDATA[<p>Joe, I&#8217;m curious as to how you are securing these services to make sure requests are only coming from the places you think it is.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
