rewrite gives 404 when directory doesn't exist

[bakiido]

I have the following problem.

Using the .htaccess file

RewriteEngine On
Options +FollowSymLinks
rewriteRule ^tasks(/?)$ index.php?op=tasks$
rewriteRule ^projects(/?)$ index.php?op=projects$

If the folders tasks/ and projects/ exist, even empty, it works fine, but if they don't exist I get 404 not found.

I not that it should be possible to do this without creating folder, what is the trick?

[g1smd]

The final $ on the very end of both lines should be removed.

The /? notation is very dangerous, creating duplicate content.

[jdMorgan]

What version of Apache are you using?

Jim

[g1smd]

Add [L] to the very end of both rules when you remove the final $ sign at the very end.

[bakiido]

version: Apache/2.2.9 (Debian) PHP/5.2.6-5 with Suhosin-Patch mod_ssl/2.2.9 OpenSSL/0.9.8g

The following rules, also don't work

RewriteRule ^tasks index.php?op=$1 [L]
RewriteRule ^projects index.php?op=$1 [L]

I have other .htaccess file on the main folder. Do you think that maybe I should put all the rules in the root(main) folder?

[g1smd]

Since no back reference is created in either rule, the $1 usage will always yield a blank value there.

You changed too many things at once, changing things that didn't need changing.

The original instruction was to remove the "dollar sign at the very end".

[bakiido]

Yes, I forgot to remove the '$1' I tried this now and also don't work.

RewriteRule ^tasks index.php?op=tasks
RewriteRule ^projects index.php?op=projects

but it works, if the folders tasks/ and projects/ exist. That it the strange thing. Isn't it?

[bakiido]

In the same file I have other rule:

RewriteRule ^$ index.php?op=overview

and this one works fine!

[bakiido]

I tried putting different name like this

RewriteEngine On
Options +FollowSymLinks
rewriteRule ^tasks1/?$ index.php?op=tasks$
rewriteRule ^projects1/?$ index.php?op=projects$

and it works.

what it is the difference between tasks1 and tasks? I remove folders with names tasks/ and projects/ from the folder. There is something blocking this two names?

[g1smd]

For the last time.

Remove the final $ sign from the very end of both of your rules.

Add [L] to the very end of both of your rules.

The /? notation is very dangerous because it creates Duplicate Content. Choose one or the other as being the valid URL for that content.

[bakiido]

I did that, but that isn't the problem.

Now, this works

RewriteRule ^overview/tasks1/$ /~pbtz/temp/sqig/overview/index.php?op=tasks

this doesn't, gives 404

RewriteRule ^overview/projects/$ /~pbtz/temp/sqig/overview/index.php?op=projects

It seems to be some problem with the name /projects
since if I change it for something else, it works.

What can be blocking the use of this name?

[bakiido]

Moreover, [L] doesn't do any difference in both cases!

[Caterham]

I remove folders with names tasks/ and projects/ from the folder. There is something blocking this two names?

If files or folders exist with that name, may be content negation. But anyway, that should not result in a 404 if negation takes place. If you don't use content negation and your server config enables MultiViews, disable the setting again:

Options -MultiViews

[bakiido]

That is the solution! thank you! :)

[jdMorgan]

And again, add [L] to all of your RewriteRules, unless you have a very good reason not to use it.

Jim

[bakiido]

OK!

Why doesn't work relative path:

RewriteRule ^tasks/$ index.php?op=tasks

Just

RewriteRule ^tasks1/$ /~pbtz/temp/sqig/overview/index.php?op=tasks

[jdMorgan]

Because you are apparently using Apache mod_userdir, and the DocumentRoot configured in your server configuration file must point to a level above the users such as "~pbtz" in order for these ~user directories to function.

Jim

[Caterham]

Why doesn't work relative path:

Use the RewriteBase directive to specify the URL-path under which you can reach the directory from "outside".
Syntax:

RewriteBase /~pbtz/temp/sqig/overview/