Closed voxsim closed 12 years ago
I found the problem: the submit of the form isn't the right way.. they hide how to submit the data.. I try to simulate the click of button "GO" but this don't do anything
You're not the first to request more error tolerance to make these server-side errors non-fatal. I will try and find a solution as soon as I find the time.
It's not your fault! It 's udacity fault and jQuery.ajax() .. I solved with javascript injection in the page (https://github.com/voxsim/udacity_downloader/blob/master/udacity.py)
@voxsim: It's nice that you could fix it on your side in this case, but dryscrape is specifically designed to be able to scrape real-world web pages, and those have bugs (which you usually can't fix on the server side).
@niklasb: Maybe you're right. Now i really don't understand how to debug dryscrape and webkit_server, i sniffed the packet traffic with wireshark. I intend to use dryscrape in various my projects, maybe I can help to fix something.
@voxsim: I usually just use cout/cerr
for C++ debugging, especially because in the case of Qt, a lot of multi-threading is going on. What we need in particular is a way to make failures on intermediate requests (CSS resources, Javascripts etc.) non-fatal, but still finish loading the page. Without looking into it myself, I can't tell you what the actual caveats might be here. I remember that the SetErrorTolerant
command was doing something similar, but it was quite a hack (and doesn't seem to work as expected in many cases).
@niklasb: ok i understand, now i have fork of dryscrape and webkit-server, if i found one way to fix some problems i can pull request and try to merge my patch, ok? (i'm new of github, but i'm old of git XD) I saw many developers working on capybara webkit-server, I'll see if they have already solved some problems.
@voxsim: Yes, that's the way it works best :) It's best to create a topic branch for work like this. Pull requests are basically just notifications of changes on a branch to the original author. I actually have to check the current status of the "real" webkit_server myself. Have contributed quite a bit to it already, but they are constantly adding new features.
Thanks for your interest and participation by the way :) It's highly appreciated!
@niklasb: Good :D I sent you an email just to talk about webkit-server and dryscrape when i'll have news and don't continue to talk about it here XD
this is my code:
and that is the output
any suggestion to resolve this problem?