<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>AjaxApp.com, ajax app and cool web apps! &#187; Security</title>
	<atom:link href="http://www.ajaxapp.com/category/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ajaxapp.com</link>
	<description>about ajax, javascript, DHTML, CSS, web app, MySQL, PHP, JSP, Java, Oracle and Howtos</description>
	<lastBuildDate>Tue, 30 Aug 2011 14:08:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>How to eliminate Mixed content security warning on your web pages</title>
		<link>http://www.ajaxapp.com/2009/10/23/how-to-eliminate-mixed-content-security-warning-on-your-web-pages/</link>
		<comments>http://www.ajaxapp.com/2009/10/23/how-to-eliminate-mixed-content-security-warning-on-your-web-pages/#comments</comments>
		<pubDate>Sat, 24 Oct 2009 04:32:40 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[How-tos]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Web Browser]]></category>

		<guid isPermaLink="false">http://www.ajaxapp.com/?p=457</guid>
		<description><![CDATA[You should have been pretty familiar with the above prompt of your web browser, especially Internet Explorer, if you&#8217;ve been involved in developing web pages for your websites that are delivered via the HTTPS secure channel. The prompt is a mixed content security warning, which was resulted due to your webpages having images, javascripts, flash [...]]]></description>
		<wfw:commentRss>http://www.ajaxapp.com/2009/10/23/how-to-eliminate-mixed-content-security-warning-on-your-web-pages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Chrome remains as the most secure brower to date, stands the first-day test of Pwn2Own</title>
		<link>http://www.ajaxapp.com/2009/03/20/google-chrome-remains-as-the-most-secure-brower-to-date-stands-the-first-day-test-of-pwn2own/</link>
		<comments>http://www.ajaxapp.com/2009/03/20/google-chrome-remains-as-the-most-secure-brower-to-date-stands-the-first-day-test-of-pwn2own/#comments</comments>
		<pubDate>Sat, 21 Mar 2009 01:52:38 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[In The news]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Web Browser]]></category>
		<category><![CDATA[Google Chrome]]></category>

		<guid isPermaLink="false">http://www.ajaxapp.com/?p=305</guid>
		<description><![CDATA[A number of security experts gathered at the contest at CanSecWest, and they&#8217;ve performed several stringent security tests at the Pwn2Own competition, on the most popular web browsers including Internet Explorer, Firefox, Safari and also Google Chrome. The first three (IE, Firefox, Safari) all went down, caught with bugs and security exploits. And only Google [...]]]></description>
		<wfw:commentRss>http://www.ajaxapp.com/2009/03/20/google-chrome-remains-as-the-most-secure-brower-to-date-stands-the-first-day-test-of-pwn2own/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to get rid of error or warning messages output by PHP in a programatic way for a production PHP web app</title>
		<link>http://www.ajaxapp.com/2008/09/22/how-to-get-rid-of-error-or-warning-messages-output-by-php-in-a-programatic-way-for-a-production-php-web-app/</link>
		<comments>http://www.ajaxapp.com/2008/09/22/how-to-get-rid-of-error-or-warning-messages-output-by-php-in-a-programatic-way-for-a-production-php-web-app/#comments</comments>
		<pubDate>Tue, 23 Sep 2008 06:08:18 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[How-tos]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Quick Tip]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[PHP Error]]></category>

		<guid isPermaLink="false">http://www.ajaxapp.com/?p=87</guid>
		<description><![CDATA[Lets say you&#8217;re on a shared hosting, or you&#8217;re only a programmer which you have NO control at all on the error warning messages output by PHP, such as those E_WARNING, E_ALL, E_STRICT etc. The easiest way to get rid of error messages in your PHP program is to add the @ operator in front [...]]]></description>
		<wfw:commentRss>http://www.ajaxapp.com/2008/09/22/how-to-get-rid-of-error-or-warning-messages-output-by-php-in-a-programatic-way-for-a-production-php-web-app/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to write your own cloaking detector in PHP</title>
		<link>http://www.ajaxapp.com/2008/09/22/how-to-write-your-own-cloaking-detector-in-php/</link>
		<comments>http://www.ajaxapp.com/2008/09/22/how-to-write-your-own-cloaking-detector-in-php/#comments</comments>
		<pubDate>Tue, 23 Sep 2008 04:08:21 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[How-tos]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Quick Tip]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[cloaking]]></category>
		<category><![CDATA[web security]]></category>

		<guid isPermaLink="false">http://www.ajaxapp.com/?p=77</guid>
		<description><![CDATA[Cloaking is black hat SEO that we always hate, especially running wordpress that always gets hacked with spam links injection at the bottom of your footer page. If you wanna detect if your blog has been hacked with cloaking a very simple PHP script as follows will do. Using the ini_set(&#8216;user_agent&#8217;,'Googlebot/2.1 (+http://www.googlebot.com/bot.html)&#8217;); to set the [...]]]></description>
		<wfw:commentRss>http://www.ajaxapp.com/2008/09/22/how-to-write-your-own-cloaking-detector-in-php/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHP + Rsync + MySQL &#8211; building your own data/file remote syncing app</title>
		<link>http://www.ajaxapp.com/2008/05/21/php-rsync-mysql-building-your-own-datafile-remote-syncing-app/</link>
		<comments>http://www.ajaxapp.com/2008/05/21/php-rsync-mysql-building-your-own-datafile-remote-syncing-app/#comments</comments>
		<pubDate>Thu, 22 May 2008 03:35:55 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Quick Tip]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.ajaxapp.com/2008/04/11/php-rsync-mysql-building-your-own-datafile-remote-syncing-app/</guid>
		<description><![CDATA[This is to show you how you can build a little rsync app in PHP that is to be run by a Linux/Unix cron job that syncs files on your data or web server to a remote server. PHP is allowed to execute the Unix/Linux system commands such as &#8220;rsync&#8221; and it gives you the [...]]]></description>
		<wfw:commentRss>http://www.ajaxapp.com/2008/05/21/php-rsync-mysql-building-your-own-datafile-remote-syncing-app/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Beware of remote code injection exploit in PHP!</title>
		<link>http://www.ajaxapp.com/2007/11/29/beware-of-remote-code-injection-exploit-in-php/</link>
		<comments>http://www.ajaxapp.com/2007/11/29/beware-of-remote-code-injection-exploit-in-php/#comments</comments>
		<pubDate>Fri, 30 Nov 2007 04:21:34 +0000</pubDate>
		<dc:creator>chris</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.ajaxapp.com/2007/11/29/beware-of-remote-code-injection-exploit-in-php/</guid>
		<description><![CDATA[PHP is kind of convenient to build web pages that have common header and footer. This is the technique we normally use when coming to building corporate web sites to maintain same look and feel over the entire websites. For example in the following piece of code (index.php), it shows you how it&#8217;s used. The [...]]]></description>
		<wfw:commentRss>http://www.ajaxapp.com/2007/11/29/beware-of-remote-code-injection-exploit-in-php/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

