| 2:17 am on Oct 2, 2009 (gmt 0)|
Because your rule requires a slash after "concerts", and you typed only "concerts" as the URL-path according to the logged info above.
| 7:33 am on Oct 2, 2009 (gmt 0)|
I´m sorry but I cannot understand. I think my rule has a slash after concerts:
RewriteRule ^concerts/(.*)$ ...................
| 7:41 am on Oct 2, 2009 (gmt 0)|
If you refers to the path written in the browser, I wrote this:
| 7:59 am on Oct 2, 2009 (gmt 0)|
He's saying from looking at the log file the URL the server was trying to find was /concerts at the end.
I'm not sure what the . on the right side of the rule is for?
RewriteRule ^concerts/(.*)$ ./index.php?section=concerts¶metros=$1 [L]
I would try:
RewriteRule ^concerts/(.*)$ /index.php?section=concerts¶metros=$1 [L]
The rewrite base is really unnecessary if you are going to use a / on the right side of the rule and the truth is it will probably do nothing more than confuse the issue, so I would go ahead and remove it.
| 11:33 am on Oct 2, 2009 (gmt 0)|
|"[Thu Oct 01 23:47:33 2009] [error] [client 127.0.0.1] File does not exist: C:/webs/MyMusicWeb/concerts |
If the rule did not work, and the logged information is correct, then the requested URL was apparently "example.com/concerts" with no trailing slash. Since this does not match your rule's pattern, the rule woould not have been invoked for this request.
Your rule looks "correct enough" and should work. Do be sure to completely flush (delete) your browser cache after changing any server-side code.
| 11:42 am on Oct 2, 2009 (gmt 0)|
I have finally solved the problem. My .htaccess was completely OK; the problem was that apache use to disable directories from having an .htaccess file.
So I have wrote these lines into the httpd.conf file:
Doing that, Apache allows "myWebDirectory" folder to have an .htaccess file.
Thanks a lot to everybody
| 11:56 am on Oct 2, 2009 (gmt 0)|
Note that since you have config access on this server, you should consider putting your rewrites in the config file, since they will be executed much more efficiently in that context than in .htaccess. The only drawback to putting the code in your config file is that it will be necessary to restart the server after any change to your rule(s).
| 12:07 pm on Oct 2, 2009 (gmt 0)|
Thanks for the information, but all of this is only to try my web appliccations in localhost, in my computer. So I do not care very much about that kind of efficiency. Anyway, thanks a lot for your consideration and for "wasting" your time solving my problems.
| 1:41 pm on Oct 2, 2009 (gmt 0)|
No problem... I'm glad you solved the "mystery" -- I hate "mysteries"... :)