Investigate Delicious + Safari interaction

Open zakj opened this issue 12 years ago • 1 comments

When a user first enters her credentials, we fire off an API request to check whether they were correct (so as to provide clean failure UI). Both Pinboard and Delicious return a 401 response on bad creds; Pinboard also includes a WWW-Authenticate header. All well and good, except that when Safari sees such a header, it pops up its own authentication UI before updating the XmlHttpRequest's readyState. As far as I can tell, there's no way for us to avoid that behavior short of setting up a credential-check proxy server, which seems like a Very Bad Idea.

Apr 24 '13 23:04 zakj

I tried to get in touch with Delicious to talk about this issue last November, but got no response.

May 01 '13 22:05 zakj