>
> As an aside, if you're using RewriteEngine anyway, you might as well use
repoze.vhm#vhm_path. The X-header stuff is mostly useful if you're using
mod_wsgi. I'm glad we're trying to fix it, though. :)
I know that. This is more natural for anyone to use though--I'm setting up a
client with thi
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
Hi Nathan,
> So it seems that VIRTUAL_URL and ACTUAL_URL end up being exactly the
> same in this setup.
Yes, that's probably to be expected.
ACTUAL_URL is basically "the URL the user sees". In a path based VHM
setup, that's http://example.com when your internal URL is
http://example.com/Virtua
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan Van Gheem wrote:
> Seems like Hanno was on the right track here.
>
> is_view_template is not working correctly because the VIRTUAL_URL is not
> getting set correctly in repoze.vhm. Basically, repoze.zope2 uses the
> environ value of "repoze.vhm
Looking at this a bit more
So it seems that VIRTUAL_URL and ACTUAL_URL end up being exactly the same in
this setup.
Also, I'm looking at the tests in the repoze.vhm package, and it seems the
only reason why the tests pass is because they are using an
incorrect PATH_INFO. I'll try and setup an
Hi Nathan,
> is_view_template is not working correctly because the VIRTUAL_URL is not
> getting set correctly in repoze.vhm. Basically, repoze.zope2 uses the
> environ value of "repoze.vhm.virtual_url" to generate the VIRTUAL_URL.
> Then the actual url is grabbed from that VIRTUAL_URL.
>
> As far
Hanno Schlichting wrote:
> On Sun, Dec 27, 2009 at 7:21 PM, Nathan Van Gheem wrote:
>> The page renders completely fine with those actions missing.
>> I stepped into the code a bit and the "plone.contentactions" viewlet isn't
>> even called when repoze.vhm is used.
>
> Hhm, the only slightly funny
Seems like Hanno was on the right track here.
is_view_template is not working correctly because the VIRTUAL_URL is not
getting set correctly in repoze.vhm. Basically, repoze.zope2 uses the
environ value of "repoze.vhm.virtual_url" to generate the VIRTUAL_URL. Then
the actual url is grabbed from th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan Van Gheem wrote:
> is it possible that it makes an invalid JSON / XML-RPC call when the
>> virtual hosting is in place? Can you see anything in Firebug about a failed
>> request?
>
> No, everything looks fine.
>
> What does render at that p
On Sun, Dec 27, 2009 at 7:21 PM, Nathan Van Gheem wrote:
> The page renders completely fine with those actions missing.
> I stepped into the code a bit and the "plone.contentactions" viewlet isn't
> even called when repoze.vhm is used.
Hhm, the only slightly funny thing about this viewlet is that
Hey Tres,
is it possible that it makes an invalid JSON / XML-RPC call when the
> virtual hosting is in place? Can you see anything in Firebug about a failed
> request?
No, everything looks fine.
What does render at that point in the page?
The page renders completely fine with those actions mi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan Van Gheem wrote:
> I'm having some very odd behavior with using repoze.zope2. The site is being
> served using repoze.vhm#vhm_xheaders filter. The correct site is served;
> however, it seems that content editors can not see the content actions
Hello,
I'm having some very odd behavior with using repoze.zope2. The site is being
served using repoze.vhm#vhm_xheaders filter. The correct site is served;
however, it seems that content editors can not see the content actions drop
down menus(Actions, Display, Add new..., etc). More specially, wh
20 matches
Mail list logo
