Skip to content

Unexpected encoded path? #157

Discussion options

You must be logged in to vote

Hey glad to hear you are giving skrape{it} a try :)
This is a valid workaround for the HttpFetcher (problem should not exist for BrowserFetcher or AsyncFetcher).

It is already fixed on the master and will be part of the 1.1.0 release that will be published within the next days.
Since version 1.1.0 the "/" workaround should not be needed anymore.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by christian-draeger
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
question Further information is requested
2 participants
Converted from issue

This discussion was converted from issue #141 on June 29, 2021 20:57.