I am now experiencing the wonders of Live Bookmarks, and have set up a shared bookmarks folder. http://www.decrem.com/bart/archives/000061.html. Now I want a private bookmarks folder. So I want to put a .htaccess file in my Movable Type blog directory. Desired behavior: - If I have a live bookmark that points to an RSS field that's access-restricted, when I click on the live bookmark, the authentication box should pop up, asking for my name and password Actual behavior: - If a live bookmark points to an RSS feed that's in a protected directory, I get an error message saying "unable to obtain feed" Workaround: - I can go to a web page in the protected area, and then Firefox will prompt me to enter the password and ID. So my feed is private, and I can gain access to it, but the behavior is somewhat clunky.

Shouldn't OS & Platform --> ALL?

I ran across a similar problem when adding a live bookmark to an intranet site that runs over https. The primary form of authentication is client certificates, but the site also allows username/password authentication in certain cases. After adding a live bookmark for the site, the live bookmarks feature would attempt to visit the site, fail the certificate login (because it never gave me the pin dialog) and drop back to username/password which would also fail. Then, the next time I would visit the site, firefox would check and find that the certificate authentication already failed once, so it goes straight into username/password mode. I never got a second chance at the certificate login unless I closed my browser and re-opened it.

A potentially prominent case of this is https://gmail.google.com/gmail/feed/atom which is an Atom feed of your Gmail inbox. Would it be possible to set a username/password for the livemark in the livemark properties?

You can do http://username:password@domain.com/directory/file.rss can't you? Works fine for Gmail.

*** Bug 280737 has been marked as a duplicate of this bug. ***

*** Bug 259451 has been marked as a duplicate of this bug. ***

Sure, putting the userid and password in the URL works fine if you want your user id and password sitting around in the unencrypted and unprotected bookmarks.html file in your profile. Not exactly a secure solution but it does work.

Nice-to-have, not critical path.

*** Bug 349608 has been marked as a duplicate of this bug. ***

sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change

This bug is very edge-casey, and comment 0 already has a workaround. The front-end team has decided not to fix this one.