apache2 mod rewrite

changes in apache 2.0 mod rewrite

[roots]

Hi...

I moved site on new server with apache 2.0 and realized that my simple rewrite doesn't work anymore.

Does anybody know what do I need to translate this rule?

RewriteEngine on
rewriteRule ^(.*)/$ index.php?date=$1 [L]

[jdMorgan]

roots,

There is no mention of changes to mod_rewrite in the Upgrading to 2.0 from 1.3 [httpd.apache.org] Apache documentation.

What is your rule supposed to do (in detail)?
What, if any, error information appears in your error log?
Are you sure that mod_rewrite is loaded and enabled?

Jim

[roots]

Rule supposed to be simple and rewrite URL form
[example.net...]
to
[example.net...]

mod_rewrite module is loaded and I tried to get log with:

RewriteLog /absolute/path/bosut/public_html/news/log/rewrite.log
RewriteLogLevel 9

but that also doesn't work...

BTW .htaccess is located in /absolute/path/bosut/public_html/news/

[edited by: DaveAtIFG at 2:29 pm (utc) on June 5, 2003]
[edit reason] Revised URLs [/edit]

[jdMorgan]

roots,

Strange... It still looks OK.

I was actually suggesting you look at your "regular" error log - the one where you would usually find 400, 403, and 404 errors logged. Often you'll find mod_rewrite syntax errors that cause 500-Server Errors listed in there.

About all I can suggest is to try something like this:

Options +FollowSymLinks
RewriteEngine on
RewriteRule ^([^/]*) /news/index.php?date=$1 [L]

You may also need to explicitly declare a RewriteBase, depending on your server setup:

RewriteBase /bosut/public_html

Note that I am "guessing" the rewritebase here - I'd have to see your error log to tell if this is correct, or even necessary. If it is not correct or necessary, it can, in fact, do more harm than good.

Jim