It's a browser problem, but I'm not sure if we are relying on historical browser behavior or if these browsers actually break the spec. I'd be interested in knowing what the spec actually says about this. The problem is, Zope challenges you when you log into /manage. The browser pops up the auth box. You log in, and your browser successfully retrieves the frameset. Since the left frame *requires* authentication, it challenges the browser which send the credentials. The right frame does not require authentication, and in fact, will *not* challenge the browser. Zope assumes that the browser will automatically send the previously established credentials for the right frame, as all browsers do except the two you mention. You get index_html because Zope calculates which views you have permission to see on the object. Since it mistakenly assumes the right frame is "anonymous" (because the browser didn't send the credentials) you see the only thing that anonymous can see, index_html. So, the question is, does the spec define this behavior? Are browsers required to send authentication information previously established for a given realm even when *not* challenged by the server? Good question. Any HTTP wizards out there? -Michel On Mon, 25 Jun 2001, Mark James Adams wrote:
Hello,
In certain browsers (OmniWeb for MacOS X and a version of IE on Windows 2000), the management screen operates incorrectly. In the main frame of the management screen, manage_workspace returns the contents of index_html instead of manage_main.
If for instance, if I view http://myzopesite/manage_workspace, I am redirected to http://myzopesite/index_html rather than the correct http://myzopesite/manage_main.
I've only encountered this error with OmniWeb and whatever version of IE was on a Windows 2000 machine I was using in one of my university's research labs.
When I first encountered the problem, I thought it was an error with my Zope installation, but the management screen works on every other browser I've encountered except these two.
Is the problem with the browser or is it something that Zope is doing? Anyone ever seen this before?
BTW, I've had this problem with both 2.3.3 (running on Linux) and 2.4b (running on MacOS X Server).
Thanks.
-- Mark James Adams mark@raysend.com
_______________________________________________ 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 )