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

wallabag can't retrieve contents for this article: osqledaren.se #2150

Closed
solarchemist opened this issue Jun 17, 2016 · 2 comments · Fixed by j0k3r/graby#63
Closed

wallabag can't retrieve contents for this article: osqledaren.se #2150

solarchemist opened this issue Jun 17, 2016 · 2 comments · Fixed by j0k3r/graby#63

Comments

@solarchemist
Copy link

solarchemist commented Jun 17, 2016

Issue details

http://osqledaren.se/ol-gor-bangladesh/

Environment

  • wallabag version (or git revision) that exhibits the issue: 2.0.5
  • How did you install wallabag? Via git clone or by downloading the package? git clone
  • Last wallabag version that did not exhibit the issue (if applicable):
  • php version: 5.6.22
  • OS: Debian Jessie
  • type of hosting (shared or dedicated): dedicated
  • which storage system you choose at install (SQLite, MySQL/MariaDB or PostgreSQL): MySQL

Steps to reproduce/test case

Pasting link into "new entry" or adding via Firefox addon v2 both fails with wallabag can't retrieve contents for this article.

@solarchemist solarchemist changed the title wallabag can't retrieve contents for this article: osqledaren.se wallabag can't retrieve contents for this article: theatlantic.com Jun 17, 2016
@solarchemist solarchemist changed the title wallabag can't retrieve contents for this article: theatlantic.com wallabag can't retrieve contents for this article: osqledaren.se Jun 17, 2016
@Strubbl
Copy link
Contributor

Strubbl commented Jun 17, 2016

Here the issue is, that the site thinks we are a crappy Internet Explorer browser. Currently graby cannot send http headers (user agent), so there is no chance to fix this at the moment.

@j0k3r
Copy link
Member

j0k3r commented Nov 7, 2016

The problem is bigger than that.
We automatically detect a refresh meta tag in the html source, because of:

<!--[if lte IE 8]>
<meta http-equiv="refresh" content="0; url=/ie.html" />
<![endif]-->

Here is the log from graby:

Meta refresh redirect found (http-equiv="refresh"), new URL: http://osqledaren.se/ie.html

Graby should remove those comment before analysing html

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

Successfully merging a pull request may close this issue.

3 participants