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

Force user-agent for iansommerville.com #1804

Merged
merged 1 commit into from Apr 8, 2016
Merged

Force user-agent for iansommerville.com #1804

merged 1 commit into from Apr 8, 2016

Conversation

j0k3r
Copy link
Member

@j0k3r j0k3r commented Mar 18, 2016

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Documentation no
Translation no
Fixed tickets #1801
License MIT

When using the default User Agent, the website returns a 403. By forcing the User Agent for this domain, we got the proper behavior: a 200

Since we can't append new user agent to the default graby configuration, we need to rewrite all the default config + the new one.

When using the default User Agent, the website returns a 403. By forcing the User Agent for this domain, we got the proper behavior: a 200

Since we can't _append_ new user agent to the default graby configuration, we need to rewrite all the default config + the new one.

Fix #1801
@j0k3r j0k3r added this to the 2.0.0 milestone Mar 18, 2016
error_message: "wallabag can't retrieve contents for this article. Please report this issue to us."
http_client:
user_agents:
'lifehacker.com': 'PHP/5.2'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll have a huge file in next weeks?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Next weeks?
We don't update that list quite often.
But I agree that this isn't greatly designed in graby (inherited from full-text-rss on that part)

@nicosomb nicosomb modified the milestones: 2.0.0, 2.0.1 Apr 3, 2016
@nicosomb
Copy link
Member

nicosomb commented Apr 7, 2016

@wallabag/core Do we need to try to move this fix in graby or can I merge?

@j0k3r
Copy link
Member Author

j0k3r commented Apr 7, 2016

This'll require too much work on graby.
This won't be done in the coming weeks.

You can merge that and we'll see later when (if ?) graby evolve, we'll update the code accordingly.

@nicosomb nicosomb merged commit 77b9db8 into v2 Apr 8, 2016
@nicosomb nicosomb deleted the j0k3r-patch-1 branch April 8, 2016 09:18
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

Successfully merging this pull request may close these issues.

None yet

2 participants