[dotnet] Utilize dedicated WebDriver Spec endpoint to get named cookie #14957
+82
−24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
NoSuchCookieException
class for cookie not found scenariosGetCookieNamed
to use specific endpoint instead of filtering all cookiesChanges walkthrough 📝
CookieJar.cs
Refactor cookie retrieval to use dedicated endpoint
dotnet/src/webdriver/CookieJar.cs
all cookies
NoSuchCookieException.cs
Add NoSuchCookieException class
dotnet/src/webdriver/NoSuchCookieException.cs
WebDriver.cs
Add NoSuchCookie error handling
dotnet/src/webdriver/WebDriver.cs
W3CWireProtocolCommandInfoRepository.cs
Update GetCookie command HTTP method
dotnet/src/webdriver/Remote/W3CWireProtocolCommandInfoRepository.cs