-
Notifications
You must be signed in to change notification settings - Fork 18
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
Support redirects instead of throwing a "HTTP 302 error" #13
Comments
Right now, redirects are not supported, so I would recommend to update your sitemap and make sure that all listed urls returns 200. But I'll keep this issue open since we should support 302/301 http statuses (but only on the same origin). |
We started to work on supporting redirects: a113ba2 |
Also added a relevant commit to this problem: a19af58 |
I would need this feature also, is it already in the latest release on npm? thx Stephan |
@wortkotze Sadly, it is still not done. But, it should be pretty easy to add now... |
@nitriques thx I used your commit and added it manually |
@wortkotze That's cool! Wanna send a PR !?!? |
node app.js is generating HTTP 302 error while accessing definition pages of my website e.g. http://www.alleydog.com/glossary/definition.php?term=Eccentricity
Other pages are being crawled successfully.
Can you please suggest some solution?
The text was updated successfully, but these errors were encountered: