Well, not always.
With Office2000 on W2000, it actually does protocol discovery, prompts for credentials, and then opens read/write.
With Office2003 on W2000, *sometimes* it just opens it read-only (with the content from IE's cache), but sometimes it starts sending OPTIONS requests (both to the document and it's parent collection).
That's interesting.
I've tried with several versions of office on windows, and when opening a document from a <href> style link, they've always just opened it as they would any document linked to from a webpage. Also, when looking for a solution to this it seems that everyone else has experienced the same thing.
I'd be interested to hear more about this as one of the problems we've been having is opening the documents in word so they can be save straight back to slide.
As Wiley Jacobs pointed out (thanks!), Microsoft has documented the behaviour in <http://support.microsoft.com/?kbid=838028>.
This also explains the behaviour I see with O2K + service packs:
"To work around this drawback, a modified approach is introduced in Office 2000 Service Release 1. Instead of trying to bind by using a publishing moniker at load time, Office binds to the document by using the typical read-only URL moniker that is provided by Internet Explorer. When you want to save the file, Office tries to switch to the publishing moniker to perform a save back to the server, if the server supports Web publishing. If re-authentication is required because of the change in session, you are prompted for credentials on save instead of on open. If you want to read the file without saving the file, Office avoids the costly switch-of-context to a publishing moniker. Office also avoids a server lock on the resource. This is a compromise approach."
I'm still investigating the following questions for O2003, though:
1) When sending the OPTIONS requests for Protocol Discovery and getting back 401 status codes, the authentication dialog does not appear on some machines. Office just keeps retrying a few times, then gives up and opens read-only.
2) For some reason, Office sends OPTIONS requests to both the parent collection and the actual document. The former seems to be useless and a waste of time.
Does anybody happen to know more about these issues? Are they possibly known issues (documented in Microsoft's KB)?
Best regards, Julian
-- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
