- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 8.6k
 
[dotnet] Utilize dedicated WebDriver Spec endpoint to get named cookie #14957
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
[dotnet] Utilize dedicated WebDriver Spec endpoint to get named cookie #14957
Conversation
          PR Reviewer Guide 🔍Here are some key observations to aid the review process: 
  | 
    
          PR Code Suggestions ✨Explore these optional code suggestions: 
  | 
    
| 
           Contributes to #15044  | 
    

User description
Description
Motivation and Context
Related to #14884
Current: Internally it fetches all cookies and then filters out on client side.
Proposed: There is special remote endpoint, so just use it.
Types of changes
Checklist
PR Type
Bug fix
Description
NoSuchCookieExceptionclass for cookie not found scenariosGetCookieNamedto use specific endpoint instead of filtering all cookiesChanges walkthrough 📝
CookieJar.cs
Refactor cookie retrieval to use dedicated endpointdotnet/src/webdriver/CookieJar.cs
all cookies
NoSuchCookieException.cs
Add NoSuchCookieException classdotnet/src/webdriver/NoSuchCookieException.cs
WebDriver.cs
Add NoSuchCookie error handlingdotnet/src/webdriver/WebDriver.cs
W3CWireProtocolCommandInfoRepository.cs
Update GetCookie command HTTP methoddotnet/src/webdriver/Remote/W3CWireProtocolCommandInfoRepository.cs