[Zope] re: Adobe GoLive and "Content-Type" HTTP header

[Jeffrey P Shell]

This has been a known issue for a long time, and it's a fault of GoLive
(although not a huge fault - I think they're just erring on the side of
caution...  maybe too far to the side) not WebDAV.  A new version of GoLive
is supposed to be in development, and I know that we've reported this bug
ourselves, so maybe if enough people scream someone will hear :).

FWIW, The 'Content-Type' element you're referring to is a WebDAV Property i=
n
this case (found through a PROPFIND command), not the HTTP Header.  Zope
doesn't always fill in the DAV property, but does fill in the header.  Case=
s
*can* exist in WebDAV where the value of the header and the property can be
different.

This quote (from an Ars Technica article on Mac OS X, which starts letting
go of the dual fork functionality of the classic Mac OS) is always poignant
to remember in this situation (for better or worse... or worse and worse an=
d
worse...):

"""
Nevertheless, the dawn of the Internet and the lowest common denominator of
simple, one-dimensional file streams that it has spread across all of
computing, even to areas that the dominance of Windows had not yet reached,
makes support for "meta-data through file name mutilation" a necessary evil=
.
""" <http://www.arstechnica.com/reviews/01q2/macos-x-final/macos-x-12.html>

It wasn't supposed to be this way, but it is.  :/

resource forks (or object databases) forever!

> From:=A0=A0Svante Kleist <svante+zope@n...>
>=20
> Chris and other GoLive fans,
>=20
> Not that I expect much from it, and mostly
> out of pure curiosity about this new phenomenon
> on the Internet, I've opened an issue with
> the new commercial support broker service at
>=20
> < "http://www.adobe.com/support" >
>=20
> (click "Adobe Support Exchange" beneath
> "Direct Support" in the lower right)
>=20
> =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D
>=20
>=20
> My WebDAV server contains HTML documents
> named without a ".htm" / ".html" suffix.
> They are served with a correct "Content-Type"
> HTTP header, which GoLive obviously reads
> since the Inspector displays "text/html"
> in the "Content Type" field.
>=20
> However, the pop-up menu for these documents
> does not contain an "Open" choice.
>=20
> Is there a way of helping stupid GoLive
> to understand that this really is an HTML
> document? When I double-click on it,
> I want GoLive to open it, and not to display
> the "Browse for Folder" dialog.
>=20
> =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D
>=20
> I'll summarize any solutions here.
Jeffrey P Shell, jeffrey@Digicool.com
http://www.digicool.com/ | http://www.zope.org