The HTTP queries generated by 0.0.18 fail to account for URL encoding and
entities in the source data. The small patch attached fixes all such issues I
could trace down, making all crawler requests for various oddball filenames
work out that I have seen in my testing.
PS: this is in no way a complete fix, and the reverse problem also exists (decoding
encoded URLs) - plus it seems to cause double-encoding in the "add" command.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=280324
PS: this is in no way a complete fix, and the reverse problem also exists (decoding
encoded URLs) - plus it seems to cause double-encoding in the "add" command.