Skip to content
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

Retrieval error #85

Closed
wjk82 opened this issue Jun 22, 2019 · 6 comments
Closed

Retrieval error #85

wjk82 opened this issue Jun 22, 2019 · 6 comments

Comments

@wjk82
Copy link

wjk82 commented Jun 22, 2019

Got this issue only on one feed.

  • ruby -v
    ruby 2.3.3p222 (2016-11-21) [i386-linux-gnu]

  • transmission-rss -v
    0.2.6

//edit: updated to v.1.0.0 and error is still an issue

Other feeds configured same as this one working fine.

@sienikam
Copy link

sienikam commented Aug 30, 2019

you need to change line 55 in aggregator.rb:

content = open(feed.url, "User-Agent" => "transmission-rss").read

@wjk82
Copy link
Author

wjk82 commented Aug 30, 2019

you need to change line 55 in aggregator.rb:

content = open(feed.url, "User-Agent" => "transmission-rss").read

Thanx, that fixed the problem for me!

@wjk82 wjk82 closed this as completed Aug 30, 2019
@nning
Copy link
Owner

nning commented Sep 1, 2019

Is the website black-listing certain user agent strings?

This change could be included into the code; would you say, there is something argueing against it?

@nning nning reopened this Sep 1, 2019
@alexfornuto
Copy link

alexfornuto commented Sep 30, 2019

you need to change line 55 in aggregator.rb:

content = open(feed.url, "User-Agent" => "transmission-rss").read

For the uninitiated, is this a file you can change after installing as a gem, or does it need to be edited before installing from source?

EDIT: I found it at /var/lib/gems/2.5.0/gems/transmission-rss-1.0.0/lib/transmission-rss/aggregator.rb

@nning
Copy link
Owner

nning commented Sep 30, 2019

I made this change a default in the current development version.

@nning nning closed this as completed Sep 30, 2019
@alexfornuto
Copy link

@nning FWIW I thought I was having the same issue, but my 403 was from the RPC connection (first time user here). But in any case, I've continued using this change and it hasn't affected me adversely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants