<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: HTTP POST or GET</title>
	<atom:link href="http://blog.testsautomation.com/2009/01/http-post-or-get-web-services-performance-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.testsautomation.com/2009/01/http-post-or-get-web-services-performance-testing/</link>
	<description>Live fast, die old...</description>
	<lastBuildDate>Wed, 19 May 2010 19:52:40 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stuart Moncrieff</title>
		<link>http://blog.testsautomation.com/2009/01/http-post-or-get-web-services-performance-testing/comment-page-1/#comment-35</link>
		<dc:creator>Stuart Moncrieff</dc:creator>
		<pubDate>Mon, 23 Feb 2009 22:29:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.testsautomation.com/?p=61#comment-35</guid>
		<description>But it is also interesting that an HTTP 404 response is much slower than a web service response.

I find that a lot of websites have missing resources on pages that developers refuse to fix because it is not visible to an end-user. Maybe there are performance implications under heavy load.

Also, there is probably a lesson in there somewhere about always putting in web_reg_finds for every request. :)

I am enjoying reading your blog. Keep up the interesting posts.

Cheers,
Stuart.</description>
		<content:encoded><![CDATA[<p>But it is also interesting that an HTTP 404 response is much slower than a web service response.</p>
<p>I find that a lot of websites have missing resources on pages that developers refuse to fix because it is not visible to an end-user. Maybe there are performance implications under heavy load.</p>
<p>Also, there is probably a lesson in there somewhere about always putting in web_reg_finds for every request. <img src='http://blog.testsautomation.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I am enjoying reading your blog. Keep up the interesting posts.</p>
<p>Cheers,<br />
Stuart.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://blog.testsautomation.com/2009/01/http-post-or-get-web-services-performance-testing/comment-page-1/#comment-33</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 23 Feb 2009 10:26:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.testsautomation.com/?p=61#comment-33</guid>
		<description>Stuart
You are right. My server (Java, Jax-WS) doesn&#039;t accept GET requests as well. I realized that I made a mistake :/ It&#039;s throwing 404 and thats why performance is better, agrrrr...

I need to delete this stupid post.
Thanks for catching it.

Waldemar</description>
		<content:encoded><![CDATA[<p>Stuart<br />
You are right. My server (Java, Jax-WS) doesn&#8217;t accept GET requests as well. I realized that I made a mistake :/ It&#8217;s throwing 404 and thats why performance is better, agrrrr&#8230;</p>
<p>I need to delete this stupid post.<br />
Thanks for catching it.</p>
<p>Waldemar</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Moncrieff</title>
		<link>http://blog.testsautomation.com/2009/01/http-post-or-get-web-services-performance-testing/comment-page-1/#comment-32</link>
		<dc:creator>Stuart Moncrieff</dc:creator>
		<pubDate>Mon, 23 Feb 2009 09:35:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.testsautomation.com/?p=61#comment-32</guid>
		<description>Hmmm. Interesting experiment. What was the software stack the web service was running on?

I would argue that a GET request that contains a body is malformed. &lt;a href=&quot;http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.3&quot; rel=&quot;nofollow&quot;&gt;Section 9.3 of RFC 2616&lt;/a&gt; says that GET data should be in the Request-URI.

I am surprised that your web service even accepts a GET request with a body, even if it is much slower. I just tried it with a web service running on ASP.NET 2.0.50727, and the request is not accepted as a web servie call.

Cheers,
Stuart.</description>
		<content:encoded><![CDATA[<p>Hmmm. Interesting experiment. What was the software stack the web service was running on?</p>
<p>I would argue that a GET request that contains a body is malformed. <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.3" rel="nofollow">Section 9.3 of RFC 2616</a> says that GET data should be in the Request-URI.</p>
<p>I am surprised that your web service even accepts a GET request with a body, even if it is much slower. I just tried it with a web service running on ASP.NET 2.0.50727, and the request is not accepted as a web servie call.</p>
<p>Cheers,<br />
Stuart.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
