Ah. Sorry to reply to my message again, but someone out there may care. My site is secured. TinyTables has a 'Query TinyTable Data' security role, which defaults to Acquire from parent (as everything does). Since no one above there has that role, it appears to end up with permissions that only allow the admin to query the data. So when I logged on as a regular user, the problem was visible. When I signed on as admin to start fixing the issue, it went away (but I was using a separate browser, so I never saw that until later). Granting authenticated users query rights fixes the problem.
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Charlie Reiman Sent: Wednesday, July 31, 2002 11:34 AM To: Charlie Reiman; zope@zope.org Subject: RE: [Zope] VirtualHostMonster and acquisition
Uh... sorry to reply to my own post. But it appears to have just started working on its own.
I hate that.
All I've done was copy the kt_trans script into a kt_test script, then modify kt_test to do spit out the absolute_url of container and context. Then I modified it to access trans_table. Much to my surprise, it had no problems accessing the table. So I tried the original script again. And lo, it worked fine. Obviously this makes me nervous but I don't see what I can do about it.
Charlie.
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Charlie Reiman Sent: Wednesday, July 31, 2002 10:40 AM To: zope@zope.org Subject: [Zope] VirtualHostMonster and acquisition
Is it possible for VHM to screw up my acquisition?
I've got a python script called kt_trans. It access a TinyTable from a directory above itself, through a PortableHole. This all works fine when directly accessed, and works under one VHM test setup. But the production system can't find the TinyTable when acccessed via the proxy feeding to VHM.
I know that's confusing, so let me further muddy things up by give you details. I have a set up like this
/clients/one/trans_table /clients/one/reports -> portable hole to /reports /clients/two/trans_table /clients/two/reports -> portable hole to /reports /reports/kt_trans -> python script that accesses context.trans_table
The use of context.trans_table works in kt_trans when I access it via:
/clients/one/reports/kt_trans
It will access client one's trans_table in this case. All well and good and it works fine when directly accessed. However, when accessed via an apache proxy feeding VHM style URLs, I can't access my trans_tables. Other zope objects are accessable without a hitch.
Most annoying of all, this only seems to happen under production which means I've got to fight with firewalls and SSL. My attempts to replicate the problem have not been successful.
Help! I need a clue stick!
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )