<?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: Kohana And AJAX (Sitting In A Tree)</title>
	<atom:link href="http://return-true.com/2009/08/kohana-and-ajax-sitting-in-a-tree/feed/" rel="self" type="application/rss+xml" />
	<link>http://return-true.com/2009/08/kohana-and-ajax-sitting-in-a-tree/</link>
	<description>Coding Tutorials, hints &#38; tips in PHP, jQuery, CSS &#38; HTML</description>
	<lastBuildDate>Thu, 29 Jul 2010 22:16:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Kohana Tutorials &#124; Der PHPler</title>
		<link>http://return-true.com/2009/08/kohana-and-ajax-sitting-in-a-tree/comment-page-1/#comment-9936</link>
		<dc:creator>Kohana Tutorials &#124; Der PHPler</dc:creator>
		<pubDate>Tue, 08 Sep 2009 02:33:59 +0000</pubDate>
		<guid isPermaLink="false">http://return-true.com/?p=992#comment-9936</guid>
		<description>[...] lesenswertes Tutorial über den Einsatz von Kohana mit Ajax auf Return [...]</description>
		<content:encoded><![CDATA[<p>[...] lesenswertes Tutorial über den Einsatz von Kohana mit Ajax auf Return [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Veneficus Unus</title>
		<link>http://return-true.com/2009/08/kohana-and-ajax-sitting-in-a-tree/comment-page-1/#comment-9427</link>
		<dc:creator>Veneficus Unus</dc:creator>
		<pubDate>Wed, 19 Aug 2009 14:02:14 +0000</pubDate>
		<guid isPermaLink="false">http://return-true.com/?p=992#comment-9427</guid>
		<description>Now that I didn&#039;t know. Thanks. :)

I guess though, that again you come across the problem I&#039;ve seen alot of people mention about checking &lt;code&gt;HTTP_X_REQUESTED_WITH&lt;/code&gt; which is that you can easily alter the HTTP request headers. I don&#039;t know if it&#039;s true, but I&#039;ve read it referenced alot on different websites.

That seems to be the best thing for now though &amp; &lt;code&gt;request::is_ajax()&lt;/code&gt; is a lot shorter than my alternative. So thanks. :D</description>
		<content:encoded><![CDATA[<p>Now that I didn&#8217;t know. Thanks. <img src='http://return-true.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I guess though, that again you come across the problem I&#8217;ve seen alot of people mention about checking <code>HTTP_X_REQUESTED_WITH</code> which is that you can easily alter the HTTP request headers. I don&#8217;t know if it&#8217;s true, but I&#8217;ve read it referenced alot on different websites.</p>
<p>That seems to be the best thing for now though &#038; <code>request::is_ajax()</code> is a lot shorter than my alternative. So thanks. <img src='http://return-true.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Menga</title>
		<link>http://return-true.com/2009/08/kohana-and-ajax-sitting-in-a-tree/comment-page-1/#comment-9425</link>
		<dc:creator>Thomas Menga</dc:creator>
		<pubDate>Wed, 19 Aug 2009 13:57:01 +0000</pubDate>
		<guid isPermaLink="false">http://return-true.com/?p=992#comment-9425</guid>
		<description>You should use the request helper...
[php]
if (request::is_ajax()) {}
[/php]
See the docs : http://docs.kohanaphp.com/helpers/request#is_ajax

But you could do something even more useful, like building an Ajax Controller, or add a route in you main template controller to ajax methods...</description>
		<content:encoded><![CDATA[<p>You should use the request helper&#8230;</p>
<pre class="brush: php;">
if (request::is_ajax()) {}
</pre>
<p>See the docs : <a href="http://docs.kohanaphp.com/helpers/request#is_ajax" rel="nofollow">http://docs.kohanaphp.com/helpers/request#is_ajax</a></p>
<p>But you could do something even more useful, like building an Ajax Controller, or add a route in you main template controller to ajax methods&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Veneficus Unus</title>
		<link>http://return-true.com/2009/08/kohana-and-ajax-sitting-in-a-tree/comment-page-1/#comment-9416</link>
		<dc:creator>Veneficus Unus</dc:creator>
		<pubDate>Wed, 19 Aug 2009 09:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://return-true.com/?p=992#comment-9416</guid>
		<description>Well as far as I&#039;ve been able to tell, I think any AJAX request coming from you also includes your session information. I could be wrong, but I use an AJAX autocomplete in an admin area which requires you to login. Since the AJAX function it access&#039; is just another controller method &amp; all methods are locked out unless you are logged in, I would assume it needs to check if you are still logged in, since it seems to pass this fine, I assume that the session for my login has been carried along too.

I haven&#039;t checked this out so I can&#039;t really tell if all that&#039;s correct, but It&#039;s my best guess as to what is going on. I guess the best security against attacks on your AJAX functions is to always escape any MySQL, which Kohana seems to do well in conjuction with it&#039;s query builder.

Again though I&#039;m still learning Kohana myself, so thank you for the input. It really gave me some things to think about. :)

P.S. I&#039;ve added a little bit to the end of the post about checking HTTP headers for AJAX requests.</description>
		<content:encoded><![CDATA[<p>Well as far as I&#8217;ve been able to tell, I think any AJAX request coming from you also includes your session information. I could be wrong, but I use an AJAX autocomplete in an admin area which requires you to login. Since the AJAX function it access&#8217; is just another controller method &#038; all methods are locked out unless you are logged in, I would assume it needs to check if you are still logged in, since it seems to pass this fine, I assume that the session for my login has been carried along too.</p>
<p>I haven&#8217;t checked this out so I can&#8217;t really tell if all that&#8217;s correct, but It&#8217;s my best guess as to what is going on. I guess the best security against attacks on your AJAX functions is to always escape any MySQL, which Kohana seems to do well in conjuction with it&#8217;s query builder.</p>
<p>Again though I&#8217;m still learning Kohana myself, so thank you for the input. It really gave me some things to think about. <img src='http://return-true.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>P.S. I&#8217;ve added a little bit to the end of the post about checking HTTP headers for AJAX requests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pablo</title>
		<link>http://return-true.com/2009/08/kohana-and-ajax-sitting-in-a-tree/comment-page-1/#comment-9405</link>
		<dc:creator>Pablo</dc:creator>
		<pubDate>Tue, 18 Aug 2009 22:33:25 +0000</pubDate>
		<guid isPermaLink="false">http://return-true.com/?p=992#comment-9405</guid>
		<description>I haven&#039;t added Ajax to my Kohana site yet but these are my thoughts. I was going to look into support for checking the AJAX header in the HTTP response, make sure it really was an AJAX request but I don&#039;t know if this is well-supported by the browsers. I was also going to see if my sessions would track across the AJAX request or if I needed to add some additional token to every request just to actually prove it came from a legitimate user and not something that was just crafted to bypass the authentication in the normal HTML.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t added Ajax to my Kohana site yet but these are my thoughts. I was going to look into support for checking the AJAX header in the HTTP response, make sure it really was an AJAX request but I don&#8217;t know if this is well-supported by the browsers. I was also going to see if my sessions would track across the AJAX request or if I needed to add some additional token to every request just to actually prove it came from a legitimate user and not something that was just crafted to bypass the authentication in the normal HTML.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
