<?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>OXT blog &#187; apache</title>
	<atom:link href="http://blog.o-x-t.com/tag/apache/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.o-x-t.com</link>
	<description>"People say nothing is impossible, but I do nothing every day." - Whinnie The Pooh</description>
	<lastBuildDate>Wed, 25 Aug 2010 19:18:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Problems with index module routing in symfony</title>
		<link>http://blog.o-x-t.com/2008/11/26/problems-with-index-module-routing-in-symfony/</link>
		<comments>http://blog.o-x-t.com/2008/11/26/problems-with-index-module-routing-in-symfony/#comments</comments>
		<pubDate>Wed, 26 Nov 2008 11:48:12 +0000</pubDate>
		<dc:creator>alex</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[symfony]]></category>

		<guid isPermaLink="false">http://blog.o-x-t.com/?p=124</guid>
		<description><![CDATA[I was working on simple symfony website consisting of just one application and one module. Naturally, I wasn&#8217;t too creative and choose &#8216;frontend&#8217; as application name and &#8216;index&#8217; for module name. When I started to test it on production, it wasn&#8217;t working at all except default action. It was giving me 404 error. After spending [...]]]></description>
			<content:encoded><![CDATA[<p>I was working on simple symfony website consisting of just one application and one module. Naturally, I wasn&#8217;t too creative and choose &#8216;frontend&#8217; as application name and &#8216;index&#8217; for module name. When I started to test it on production, it wasn&#8217;t working at all except default action. It was giving me 404 error.<br />
After spending some time debugging and logging symfony and mod_rewrite I&#8217;ve found out the problem. Rewrite rule was sending me to /index.php/actionname instead of index.php/index/actionname.<br />
The problem was in apache option MultiViews, as soon as I removed it everything started to work as expected. This option tells webserver to search for foo/filename.* if foo/filename wasn&#8217;t found.<br />
I had this option enabled in my default virtual host config in my apache distribution and I had never paid any attention to it before.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.o-x-t.com/2008/11/26/problems-with-index-module-routing-in-symfony/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>403 error after installing Mongrel with Apache2</title>
		<link>http://blog.o-x-t.com/2007/11/13/403-error-after-installing-mongrel-with-apache2/</link>
		<comments>http://blog.o-x-t.com/2007/11/13/403-error-after-installing-mongrel-with-apache2/#comments</comments>
		<pubDate>Tue, 13 Nov 2007 20:30:16 +0000</pubDate>
		<dc:creator>alex</dc:creator>
				<category><![CDATA[Operating systems]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[Mongrel]]></category>
		<category><![CDATA[rails]]></category>

		<guid isPermaLink="false">http://blog.o-x-t.com/2007/11/13/403-error-after-installing-mongrel-with-apache2/</guid>
		<description><![CDATA[If you&#8217;ve installed Mongrel for your Rails application with Apache2 as a proxy and receive 403-Forbidden error, first look in apache error log. If you have something like [warn] proxy: No protocol handler was valid for the URL. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;ve installed Mongrel for your Rails application with Apache2 as a proxy and receive 403-Forbidden error, first look in apache error log. If you have something like</p>

<div class="wp_syntax"><div class="code"><pre class="text" style="font-family:monospace;">[warn] proxy: No protocol handler was valid for the URL. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.</pre></div></div>

<p>you probably forgot to enable/load all required modules. Make sure you have proxy, proxy_balancer and proxy_http.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.o-x-t.com/2007/11/13/403-error-after-installing-mongrel-with-apache2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
