> Jeff,
> yep that sounds right. It would also work if you were to
> use the <Location> tag and a 'default' context. Either way
> its the same thing.
I tried the <Location> tag, but it didn't seem to work. It forced me
to put something, a context, between the host and the page. For
example, http://mysite.com/Home.py was treated internally as
http://mysite.com/Home.py/index.py and a relative link to say
"Help.py" went to http://mysite.com/Home.py/Help.py. This only worked
because my default context was the context I wanted and "Home.py"
didn't match any existing contexts. This is also true if you don't
put ".py" anywhere, I just use it because it makes it clearer what is
going on. If any of this sounds incorrect, let me know and I can test
it again.
> ----------------
> Hey Tavis, that almost worked, I looked back into the mail
> archives
> and found your post from June 3rd where you offered the
> solution but
> without the <Location /WK> part. I removed the Location
> directive and
> now the RewriteRule works. You the man! :)
>
> Oh yeah, the trick is, the WK part should really be the
> context name
> (or make it anything and let the default context be served):
> RewriteRule ^/(.*) /mycontext/$1
>
> Does that sound right?
>
> Thanks,
> Jeff
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
