You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chrome (and probably other things) sometimes generate curl commands with a $-prefixed data string, probably when it's easier to represent the string in that way or when it includes non-ASCII characters, e.g. the DiscoverQueryRendererQuery XHR on https://500px.com/popular is copied as
scrapy.utils.curl.curl_to_request_kwargs() isn't smart enough to understand this kind of shell escaping, so it puts $ into the request body which is incorrect. Ideally we should support this, though I don't know if there are existing libraries to unescape this.
The text was updated successfully, but these errors were encountered:
Chrome (and probably other things) sometimes generate curl commands with a $-prefixed data string, probably when it's easier to represent the string in that way or when it includes non-ASCII characters, e.g. the DiscoverQueryRendererQuery XHR on https://500px.com/popular is copied as
, most likely because of
\u0021
in this payload.scrapy.utils.curl.curl_to_request_kwargs()
isn't smart enough to understand this kind of shell escaping, so it puts$
into the request body which is incorrect. Ideally we should support this, though I don't know if there are existing libraries to unescape this.The text was updated successfully, but these errors were encountered: