<?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>Luc de Louw&#039;s Blog &#187; Unix</title>
	<atom:link href="http://blog.delouw.ch/category/unix/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.delouw.ch</link>
	<description>An IT guy is blogging</description>
	<lastBuildDate>Fri, 20 Jan 2012 05:09:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Oracle ditches OpenSolaris</title>
		<link>http://blog.delouw.ch/2010/08/15/oracle-ditches-opensolaris/</link>
		<comments>http://blog.delouw.ch/2010/08/15/oracle-ditches-opensolaris/#comments</comments>
		<pubDate>Sun, 15 Aug 2010 11:28:51 +0000</pubDate>
		<dc:creator>Luc de Louw</dc:creator>
				<category><![CDATA[Unix]]></category>
		<category><![CDATA[Opensource]]></category>
		<category><![CDATA[Solaris]]></category>

		<guid isPermaLink="false">http://blog.delouw.ch/?p=510</guid>
		<description><![CDATA[OpenSolaris was dropped by Oracle As many people already suspected, Oracle will ditch OpenSolaris as announced here: OpenSolaris cancelled, to be replaced with Solaris 11 Express. The first Solaris 11 Express release is expected end of this year. If is has similar usage restrictions like the Oracle 10 Express database then it will be quite [...]]]></description>
		<wfw:commentRss>http://blog.delouw.ch/2010/08/15/oracle-ditches-opensolaris/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ready to upstart?</title>
		<link>http://blog.delouw.ch/2009/10/31/ready-to-upstart/</link>
		<comments>http://blog.delouw.ch/2009/10/31/ready-to-upstart/#comments</comments>
		<pubDate>Sat, 31 Oct 2009 09:37:08 +0000</pubDate>
		<dc:creator>Luc de Louw</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Red Hat]]></category>
		<category><![CDATA[SUSE]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[RHEL]]></category>
		<category><![CDATA[RHEL6]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[Upstart]]></category>

		<guid isPermaLink="false">http://blog.delouw.ch/?p=58</guid>
		<description><![CDATA[It is time to replace the aged SysV init system with someting better At the time when  SysV init (pronounced &#8220;System five&#8221;) appeared, hardware configurations have been quite static, no hot plug and similar fancy stuff. SysV init is started after the kernel is loaded. The init process reads /etc/inittab and walks trough the runcontrol [...]]]></description>
		<wfw:commentRss>http://blog.delouw.ch/2009/10/31/ready-to-upstart/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>302 Redirects behind SSL-terminating proxies</title>
		<link>http://blog.delouw.ch/2009/10/29/302-redirect-behind-ssl-terminating-proxies/</link>
		<comments>http://blog.delouw.ch/2009/10/29/302-redirect-behind-ssl-terminating-proxies/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 20:59:09 +0000</pubDate>
		<dc:creator>Luc de Louw</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Red Hat]]></category>
		<category><![CDATA[SUSE]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[Web Servers and Applications]]></category>
		<category><![CDATA[Apache]]></category>

		<guid isPermaLink="false">http://blog.delouw.ch/?p=9</guid>
		<description><![CDATA[You have a web site all with SSL. There is a reverse proxy or load balancer that acts as SSL termination point. Behind that reverse proxy you have an Apache web server running plain http.

Your application uses 302 redirects to announce new URLs or whatever the reason is for doing so. Since the web server does not know that https URLs should be announced the response header looks like following:
<blockquote>Location <code>http://www.example.com/your-fancy-url</code></blockquote>
The browser interprets that location header and send a request to this non-SSL URL instead of https://<code>/www.example.com/your-fancy-url </code>]]></description>
		<wfw:commentRss>http://blog.delouw.ch/2009/10/29/302-redirect-behind-ssl-terminating-proxies/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

