<p>Have a look at the <a href="http://buildwithcraft.com/docs/routing" rel="nofollow">Routing article</a> in the Craft Documentation, it describes why Craft handles these request in the first place:</p>

<blockquote>
  <p>The <strong>.htaccess</strong> file that comes with Craft will redirect all would-be 404 requests over to index.php behind the scenes, which is why Craft is able to respond to URLs that don’t point to any actual folder/file in your web root.</p>
</blockquote>

<p>A fresh Craft install's <code>.htaccess</code> file looks like so:</p>

<pre><code>&lt;IfModule mod_rewrite.c&gt;
    RewriteEngine On

    # Send would-be 404 requests to Craft
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} !^/(favicon\.ico|apple-touch-icon.*\.png)$ [NC]
    RewriteRule (.+) index.php?p=$1 [QSA,L]
&lt;/IfModule&gt;
</code></pre>

<p>You'll notice that favicons are removed from the redirect. Add a similar <code>RewriteCond</code> for <code>blog/</code> to also exclude request to your  WordPress folder from this condition. </p>

<pre><code>    RewriteCond %{REQUEST_URI} !blog [NC]
</code></pre>

CC BY-SA 3.0
2014-08-16T23:08:14.557Z
You are a machine, @carlcs.
Brad Bell
CC BY-SA 3.0
2014-08-16T23:07:43.317Z
2014-08-16T23:07:43.317Z
carlcs
<p>Unfortunately, I'm in a position where I need to run a Craft and WordPress installation out of the same directory. The WordPress install is under the sub-directory <code>/blog</code>.</p>

<p>When I visit <code>http://mysite.dev/blog/</code> the WordPress blog loads as expected, but attempts to visit any routes within that result in Craft's 404 page. For instance, <code>http://mysite.dev/blog/my-post</code>.</p>

<p>Is it possible to convince Craft to ignore any requests under <code>/blog</code>? </p>

<routes>
Is it possible to tell Craft to ignore requests to under a certain path?
# Is it possible to tell Craft to ignore requests to under a certain path?

(Asked by: username_0 on 2014-08-16)

Unfortunately, I'm in a position where I need to run a Craft and WordPress installation out of the same directory. The WordPress install is under the sub-directory `/blog`.

When I visit `http://mysite.dev/blog/` the WordPress blog loads as expected, but attempts to visit any routes within that result in Craft's 404 page. For instance, `http://mysite.dev/blog/my-post`.

Is it possible to convince Craft to ignore any requests under `/blog`?

**Tags:** routes


---

## 1 answers

### Answer by username_1 on 2014-08-16. Score: 4 | Accepted answer

Have a look at the Routing article in the Craft Documentation, it describes why Craft handles these request in the first place:

The .htaccess file that comes with Craft will redirect all would-be 404 requests over to index.php behind the scenes, which is why Craft is able to respond to URLs that don’t point to any actual folder/file in your web root.

A fresh Craft install's .htaccess file looks like so:

    RewriteEngine On

    # Send would-be 404 requests to Craft
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} !^/(favicon\.ico|apple-touch-icon.*\.png)$ [NC]
    RewriteRule (.+) index.php?p=$1 [QSA,L]


You'll notice that favicons are removed from the redirect. Add a similar RewriteCond for blog/ to also exclude request to your  WordPress folder from this condition. 
    RewriteCond %{REQUEST_URI} !blog [NC]

> **Comments:**
> **username_2**: You are a machine, @username_1.  

---

