<?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>Rseven Blog &#187; Service Status</title>
	<atom:link href="http://blog.rseven.com/category/service-status/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.rseven.com</link>
	<description>a lifecache service</description>
	<lastBuildDate>Thu, 10 Jun 2010 09:18:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Certificate Issue</title>
		<link>http://blog.rseven.com/certificate-issue/</link>
		<comments>http://blog.rseven.com/certificate-issue/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 12:25:19 +0000</pubDate>
		<dc:creator>Hisyam Halim</dc:creator>
				<category><![CDATA[Service Status]]></category>

		<guid isPermaLink="false">http://202.9.98.54/blog/?p=27</guid>
		<description><![CDATA[Yes, we are trying to resolve the certificate renewal problem, it&#8217;s taking longer than expected. If you&#8217;re not comfortable using the non-encrypted HTTP to access rseven.com, please wait until we fix this. I&#8217;m sorry about this, it&#8217;s our bad. [Updated] It&#8217;s fixed, the certificate is ok now, Rseven is back on secure HTTP.]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fblog.rseven.com%2Fcertificate-issue%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fblog.rseven.com%2Fcertificate-issue%2F&amp;source=rsevenmobile&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>Yes, we are trying to resolve the certificate renewal problem, it&#8217;s taking longer than expected. If you&#8217;re not comfortable using the non-encrypted HTTP to access rseven.com, please wait until we fix this.</p>
<div>I&#8217;m sorry about this, it&#8217;s our bad.</div>
<div>[Updated] It&#8217;s fixed, the certificate is ok now, Rseven is back on secure HTTP.</div>
]]></content:encoded>
			<wfw:commentRss>http://blog.rseven.com/certificate-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
