-
Notifications
You must be signed in to change notification settings - Fork 109
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
DeviceDetector#library? method #41
base: develop
Are you sure you want to change the base?
Conversation
@YAGoOaR any thoughts or objections? |
Just to be sure on this: what would be your use case for it? |
@YAGoOaR similar to the |
@wallin Thanks, but my question was more about in what context would one need that? Why would you need to detect a request library? Security? Blocking possible attackers? |
@YAGoOaR mostly as a very crude way of detecting scripted access (for content scraping etc.). Obviously, it's easy to change the UserAgent so this would only detect the ones that don't even bother. |
@YAGoOaR any input? |
I feel that it's a bit niche, yet I don't see the reason why it couldn't have a place in the gem. Now some thoughts: I think the code should work similar to the one in the The name of the method What do you think? |
Sorry for the belated response @YAGoOaR, got caught up in other work.
Great, thanks
Sounds good to me. But just to confirm, this will make
I a sense yes, eg. |
@YAGoOaR any new ideas on method name? and are you ok with the changed behavior for |
So we need to stick with this definition. I like |
Ok, so I assume this needs to be fixed for recognized bot UserAgents as well then? (in a separate PR of course)
Good. I'll go with that |
@YAGoOaR can this be merged? |
@nijikon We are still waiting for changes to be done by @wallin @wallin I think that |
Expose functionality to determine whether a UserAgent is a known request library