Ian Bicking wrote:
> jose@... wrote:
>> one of our applications makes extensive use of self.forward and with
>> ExtraPathInfo turned on when I use
>> self.forward('catalog.py') I get a
>> error stating that /WK/catalog.py can not be found.
>> so far this is the only error that i have seen, admittedly I have not
>> done much testing with ExtraPathInfo turned on. Should self.forward
>> be effected by ExtraPathInfo?
> Hmm... I guess I'm not surprised. It's one of the problems with
> ExtraPathInfo and the normal behavior using two entirely separate
> algorithms for finding servlets -- they differ in small, subtle ways.
> And .forward was always a little funky in how it determined
> context and
> resolved relative links, so it's not surprising a problem
> would show up
> Besides delving into the source and finding the bug (and that
> particular code ain't pretty), I suspect you're best bet will be to
> run two separate AppServers.
You're right, that code ain't pretty, and also it's changed between 0.8.1
and the tip of CVS. It might work in one but not the other.
If you are using Apache, then instead of fixing the bug or using 2
appservers, you might consider using a mod_rewrite trick in Apache so that
you don't need ExtraPathInfo. I think the Wiki may have some examples, but
basically you need to rewrite:
then just use self.request().field('extra_path_info') to get the info.