As part of my app engine app, I'm trying to implement a WebDAV server so that users can interact with my app's blobstore using their native desktop file browser (i.e., Mac Finder.app and Windows Explorer.exe).
WebDAV clients, per RFC 4918, authenticate (if at all) via HTTP Digest authentication, and I can see that I could implement this authentication method in my app only if I forego my preference for Google accounts in my app. As it is, when delegating authentication to Google accounts, Finder.app (as WebDAV client) can't correctly process the HTML authentication form that is presented on the initial request. It would be really great for my use case if some means could be added, maybe in the app.yaml handlers section, to configure HTTP Digest authentication for a chosen request path. It seems to me that the same mechanism that is currently available, that checks for a session cookie and issues the redirect to the Google account login form could instead supply the HTTP Digest nonce and challenge, along with the 401 status response to the initial unauthenticated request. I suspect there are other use cases that would benefit by an HTTP Digest authentication option, and I'm curious to know if there are other developers who want this, and what's the likelihood AppEngine will eventually incorporate such an option? Even better would be if someone could explain how I can already do this using existing support in AppEngine :) Thanks, Tommy K -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/4nzRzuJrYbIJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
