Here's how I fixed it:
# we skip all files with .something
RewriteCond %{REQUEST_URI} \..+$
RewriteCond %{REQUEST_URI} [EMAIL PROTECTED]
RewriteCond %{REQUEST_URI} !\.html$
RewriteRule .* - [L]
So if the URL has a @ in it, it is passed to the controller.
Not sure if this is the ideal solution, but it works for now.
On Fri, Sep 12, 2008 at 3:46 AM, Eno <[EMAIL PROTECTED]> wrote:
>
> On Thu, 11 Sep 2008, Dmitry Nesteruk wrote:
>
>> yes, I get a 404 error. What should I change? Can you write some example?
>
> I can't give you a generic example because it depends on the routing in
> your application.
>
> Right now, the rewrite rules will pass almost anything with a "." in it to
> Apache instead of your front controller, so you'll have to rewrite it to
> only pass what you want through to Apache. This means having to add
> explicit conditions (i.e. RewriteCond) to ONLY pass .js, .css, .jpg, .gif
> (etc etc) to Apache and leave anything else to your controller. Maybe
> something like this (this is untested, off the top of my head, so they may
> or may not work for you).
>
> RewriteCond %{REQUEST_URI} \.js$
> RewriteCond %{REQUEST_URI} \.css$
> RewriteCond %{REQUEST_URI} \.jpg$
> RewriteCond %{REQUEST_URI} \.gif$
> RewriteCond %{REQUEST_URI} \.swf$
> RewriteCond %{REQUEST_URI} \.html$
> RewriteRule .* - [L]
>
> In one of our applications, we have .html in our routing so we have
>
> RewriteCond %{REQUEST_URI} !\.html$
>
> in our rules. You will need to test and adjust accordingly based on yhe
> routing in your application.
>
>
>
> --
>
>
>
> >
>
--
Visit my website: http://onlinesid.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---
