Chris McDonough wrote:
> Martin Aspeli wrote:
>>> I assumed it was just acquisition trickery. Looking more closely,
>>> z2bob.py uses the repoze.vhm.virtual_root via the getVirtualRoot in the
>>> repoze.vhm.utils package to get the virtual root and it seems to create
>>> the correct path for traver
Martin Aspeli wrote:
>>
>> I assumed it was just acquisition trickery. Looking more closely,
>> z2bob.py uses the repoze.vhm.virtual_root via the getVirtualRoot in the
>> repoze.vhm.utils package to get the virtual root and it seems to create
>> the correct path for traversal regardless of the issu
Nathan Van Gheem wrote:
> So - this looks identical to the "vanilla" example (VIRTUAL_URL,
>
> ACTUAL_URL, URL). Does this configuration work as expected?
>
> Yes.
As an aside, if you're using RewriteEngine anyway, you might as well use
repoze.vhm#vhm_path. The X-header stuff is mostly u
>
> So - this looks identical to the "vanilla" example (VIRTUAL_URL,
ACTUAL_URL, URL). Does this configuration work as expected?
Yes.
In your case, PATH_INFO is /a/b/c/d/@@testing. I would've expected it to
be /example/a/b/c/d/@@testing, as it is in the first two examples.
exactly
perhaps rep
Nathan Van Gheem wrote:
> Thanks for the feedback on this. I've set up some tests that I
> think illustrate what is going on pretty well.
>> We can get you svn access for sure. :)
> How can I go about getting that?
Email Chris McDonough. At least that's what I did. ;)
> Here are the test result
Maybe I should have explained the tests better then.
All the requests are for the url http://example.com:/a/b/c/d/@@testing and
the plone site as located at "/example" from the zope root.
OK, to analyze the "traditional" Apache + Zope setup: you are asking
for requests to 'http://example.co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan Van Gheem wrote:
> Thanks for the feedback on this. I've set up some tests that I
> think illustrate what is going on pretty well.
>
>> What ends up happening in the current situation is that a url of
>
>> "/a/b/c/d" get chopped off to somethi
Thanks for the feedback on this. I've set up some tests that I
think illustrate what is going on pretty well.
> What ends up happening in the current situation is that a url of
> "/a/b/c/d" get chopped off to something like "/b/c/d" NOT including the
> virtual root.
> Sorry, where is this happ
