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

Problem with escaped fragment when fetching some websites #48

Closed
Antoninum opened this issue Apr 27, 2016 · 1 comment · Fixed by #101
Closed

Problem with escaped fragment when fetching some websites #48

Antoninum opened this issue Apr 27, 2016 · 1 comment · Fixed by #101

Comments

@Antoninum
Copy link

Hello !

I come from Wallabag, which is using this project.

I have problem retrieving content from a webpage, because graby automatically adds an ?_escaped_fragment_= at the end of the URL, for crawling AJAX purpose.
That's a problem because the website in question gives a 404 error when detecting this escaped fragment. Probably to avoid being fetched by robots ?

Still, the content seems to be accessible without the fragment.

A solution would be to try to fetch again the URL without this escaped fragment if a 404 error is answered ?

Here is the website, you can test with or without the escaped fragment:
https://dzone.com/
https://dzone.com/?_escaped_fragment_=

Thank you !

Antonin

@j0k3r
Copy link
Owner

j0k3r commented May 11, 2017

This is related to that issue #19
I thought all Angular websites handled _escaped_fragment_ but it seems that not all of them.

  • the smart solution: test with escaped fragment and if it failt, remove it and try again
  • the fastest one: remove the Angular detector (which add the escaped fragment)

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.

2 participants