Its working.

Barney, you were correct in your assumption of adding the PT flag.  Adding
that worked as expected.

Thanx guys!

I love this list.

On 8/23/06, Scott Stroz <[EMAIL PROTECTED]> wrote:
>
> Barney/Joseph,
>
> I have logging on, and if I am reading it correctly, the URL is being
> rewritten correctly.
>
> For example:
>
> applying pattern '^/event/(.*)$' to uri '/event/test'
> rewrite /event/test -> /index2.cfm?event=test
> split uri=/index2.cfm?event=test -> uri=/index2.cfm, args=event=test
>
> I'll try dropping this into .htaccess and see what happens.
>
>
>
> On 8/23/06, Joseph Lamoree <[EMAIL PROTECTED]> wrote:
> >
> > On 23 Aug 2006, at 12:13, Scott Stroz wrote:
> >
> > > However, when I try to redirect to a .cfm page, I get the following:
> > >
> > > <head><title>JRun Servlet Error</title></head><h1>403 Forbidden</
> > > h1><body>
> > > Forbidden</body>
> >
> > I have encountered this before. I did some Googling at the time, but
> > I don't believe I found the cause of the problem.
> >
> > What I ended up doing was moving my RewriteRules from $APACHE/conf/
> > httpd.conf to an .htaccess file in the root of the virtual web server
> > that I wanted to set URL rewriting rules. For some reason, that
> > solved the problem. Just keep in mind that the expressions that you
> > use for matching will be slightly different when they are evoked from
> > an .htaccess file. The best bet is to turn on RewriteLog logging so
> > you can see what's going on.
> >
> > --
> > Joseph Lamoree
> >
> >
> >
> > 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four 
times a year.
http://www.fusionauthority.com/quarterly

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:250786
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to