mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
HTTPS RSS feeds broken #5
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mbs on GitHub (Aug 11, 2012).
SSL support not apparently working. HTTPS RSS feeds show a red x and do not update.
Seen in Windows release version 3.0.0
@cdumez commented on GitHub (Aug 11, 2012):
Interesting. I thought Hammered had fixed this in v3.0.0. I'll ping him about this. Basically, I think Qt was compiled without SSL support.
@cdumez commented on GitHub (Aug 12, 2012):
I can confirm there is no issue on Mac OS X with the following feed: EZRSS.
Hopefully, I'm right about the Qt build issue and Hammered (Our Windows packager) can fix his build. I have tried to ping him but he has not replied yet, he may be on vacation.
@cdumez commented on GitHub (Aug 12, 2012):
BTW, could you maybe port the feed link here? or send it to me by email? (chris(at)qbittorrent(dot)org).
Note that some RSS feeds require cookies to work. Please try the RSS feed I provided to check if it works for you (I'm sure this one does not requires any cookie, although you might need to refresh it a few times to get it to work since the RSS feed server seems overloaded).
@mbs commented on GitHub (Aug 20, 2012):
Tested a couple of regular https feeds e.g. the one you mentioned and had no trouble. My other feed has a cookie and that remains broken in 3.0.0. Can't share the link. Not sure I have a way of testing whether the cookie is supplied without building up my own https server somehow.