[Zope] Difference between zope and apache
Mon, 28 May 2001 14:14:05 +0200
comparing Apache with Zope is like comparing apples with
Although some objects in Zope are called "Folder" and some
"Documents" or even "Files" these are all objects.
if you use the URL /a/b/c you traverse a path to
object c as subobject of b which is in turn subobject
If an object is called, its method index_html (by convention)
is normally invoked.
This method can (like all others) be acquired down the path,
meaning, if you have one index_html as method of the root
Folder object, you have it virtually on any sub-folder object
unless you create a new one there which is like "overloading"
a method. (see documentation on OOP)
Anyway, /a/b/c is equal to /a/b/c/ in Zope.
Unlike apache it does not have to redirect (which can be turned
of on apache too)
Just link to /a/b/c/ if it bothers you.
You might want to use <link rel=stylesheet type=text/css href="<dtml-var
To always get the right URL.
--On Montag, 28. Mai 2001 09:01 +0200 Jan-Frode Myklebust
> I've just noticed an annoying difference in the handling of directories
> in zope. If I create an directory /myDirectory, put an index_html file
> there, and a my.css file the index_html should use in the same directory
> refering to it with <link rel=stylesheet type=text/css href="my.css"> in
> the head of my document I get a structure that would work perfectly fine
> in apache, but not in zope.
> Accessing http://example.com/myDirectory in zope would give me the
> files http://example.com/myDirectory/index_html and
> In apache the server would return a location header like:
> Location: http://example.com/myDirectory/
> and then my browser would know it should ask for
> Zope doesn't seem to set the location header, so asking for
> returns different results if the index_html contains relative URLs
> below /myDirectory/.
> Bug or feature?
> Zope maillist - Zope@zope.org
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope-dev )