-
Notifications
You must be signed in to change notification settings - Fork 451
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
Bad request to Splash & HTTP status code is not handled or not allowed #168
Comments
the 'Bad request to splash' error maybe caused by 'local last_response = entries[#entries].response', but i don't konw how to fix it. |
I have a similar issue. For some requests which I make, |
Yeah, it can be the problem. It is caused by cache: when response is fetched from an in-memory cache, it doesn't get a record in splash:history. I don't have a good workaround now; it makes sense to check if history is not empty before taking last entry. |
@kmike I am fine to disable cache (in fact, I would prefer to do that). It seems like it's not possible until scrapinghub/splash#339 is merged? Related issues: scrapinghub/splash#203, scrapinghub/splash#519. |
hi kmike, i use scrapy-splash and meet a issue, when i first run 'scrapy crawl toutiao', it's run right, bug when i run it's second, it occur a issue.
i find the issue because headers i add, when i not use headers, it's run right, but it's errors when i use headers and run the second.
the lua script and project follows, i need your help, thanks.
code:
the first run correct:
the second run error:
The text was updated successfully, but these errors were encountered: