Skip to content
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

Changed errorType to message for EyeEm #2142

Merged

Conversation

pandyah5
Copy link
Contributor

@pandyah5 pandyah5 commented May 29, 2024

This PR aims to solve the false positive issue for the EyeEm website as mention in #2126

Debugging the issue:
I glanced through the code and the issue for EyeEm seems to be in the detection algorithm. The errorType is set to status_code, however a simple curl request to an unavailable username in EyeEm shows the response code as 200.

Potential solution
All unavailable usernames are accompanied by the error message:

"Whoops! We can't find the page you're looking for..."

If you wish I can make a PR for making this change and fixing it for this website. I understand that error message is the least reliable detection mechanism hence if you have better ideas I am all ears for it.

Validating the fix
Here is a screenshot verifying that EyeEm does not show up when the username is not available
image

@ppfeister ppfeister added the false positive A site is responding with false positives label May 29, 2024
@ppfeister ppfeister merged commit 945a364 into sherlock-project:master May 29, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
false positive A site is responding with false positives
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants