-
Notifications
You must be signed in to change notification settings - Fork 51
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
Netflix search doesn't work #207
Comments
Write that to the Netflix.
We don't have control of how the sites encode urls, here we don't encode urls.
Not a bug in general, it's a bug with Netflix entry. |
My apologies for not cluing in that no escaping was being done. Maybe I'm still missing something, but that would seem to be a more general problem for movie titles containing other characters that are not legal or have special meaning in URLs (eg. '%', '#', accented characters, non-ASCII, etc), for all sites, not just Netflix. Anyway, for Netflix its own search functionality generates URLs using %20 for spaces. Example:
I guess this means your Netflix entry does need a spaceEncode key just like for Netflix-DVD, or maybe '%20'? I'm afraid I don't know how to submit a PR. |
Yes, searching by the title is always wonky. Best is if a site supports searching by IMDb ID.
Test what works, I can't.
It's simple, look there -> #209 |
Thank you :-) I'm using a somewhat unusual browser configuration, so that likely explains why I'm seeing steps a little different than you. |
I think there is a bug pertaining to how search strings are being escaped. For example, with the Netflix icon site enabled, I visit
https://www.imdb.com/title/tt8002382/reference
and then click the Netflix icon, which leads me to
https://www.netflix.com/search?q=The%2BMarsh%2BKing%27s%2BDaughter with no match found. The reason is made clear by the contents of the Netflix page search box, which shows:
Those '+' characters should be spaces, like this:
A search query in a URL can encode a space as '+' or %20, but %2B is always incorrect as that is insisting the movie title actually has '+' characters in it. If I'm understanding
https://stackoverflow.com/questions/1634271/url-encoding-the-space-character-or-20,
then it's best to just not use the '+' character for space encoding and just stick to percent-encoding for everything in the query string?
The text was updated successfully, but these errors were encountered: