-
Notifications
You must be signed in to change notification settings - Fork 532
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: support for feeds behind HTTP auth #502
Comments
Agreed, really need to have http auth supported for feeds. |
Just confirming this issue still exists in Version 5.0 that just came last week. It's one of two issues blocking me from upgrading from version 4.x |
Adding my voice here that I think supporting private feeds would be very valuable. I'm working on a private blog project (https://havenweb.org) that exposes private feeds, it would be great if I could tell people that they can use NetNewsWire! |
I'd like to echo on this. It's worth adding this feature. It would make it much more powerful. Thanks. |
I also ended up here, shattered that there is no support. How I would love to see it implemented: Just a checkbox in the Info window "use auth". |
I'm surprised that this function has not been implemented yet. |
I thought I'd save my articles to Pocket and then use the RSS feed they export to load all the saved articles to my favorite place where to read stuff, the NetNewsWire. The feeds are password-protected unless I decide to open them to public (with a very guessable URL). Just noting it down here as a vote to implement this feature, which is more than just a thumbs up, but also has some background "why do you need this" explained. |
I tried to subscribe to a feed on an issue tracker that requires http auth so it knows which tickets I'm allowed to see in the activity feed, and and it wouldn't add it because "Can't add a feed because no feed was found", without ever prompting me for the user/password. If I visit the url manually in a private browsing window in the web browser I get prompted for the password and then see the xml.
The text was updated successfully, but these errors were encountered: