You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If Content-Length header is not set in request then IEDriver is not able to process the request. The other problem is that the check for Content-Lenght is case sensitive. This is not inline with HTTP specification.
I am happy to contribute the improvements if you agree with fixing this. But my C++ experience is very limited :(
Environment
OS: Windows 10
Browser: Internet Explorer
Browser version: 11
Browser Driver version: 3.14.0.0 (64-bit)
Language Bindings version: NodeJS
The text was updated successfully, but these errors were encountered:
mucsi96
changed the title
[IEDriver] No property named 'capabilities' or 'desiredCapabilities' found in new session request body. if Content-Length is not set
[IEDriver] Error: No property named 'capabilities' or 'desiredCapabilities' found in new session request body. if Content-Length is not set
Feb 2, 2020
According to RFC 2616 and 7230, headers names are case insensitive.
When creating a new session, the webdriver server is checking the
request for a case sensitive Content-Type header. This causes the body
to be empty on session creation and will result in the IEDriverServer
complaining about missing capabilities.
This change will search for the Content-Type in a case insensitive
manner before capturing the value of the header.
FixesSeleniumHQ#7986
馃悰 Bug Report
If
Content-Length
header is not set in request then IEDriver is not able to process the request. The other problem is that the check forContent-Lenght
is case sensitive. This is not inline with HTTP specification.I am happy to contribute the improvements if you agree with fixing this. But my C++ experience is very limited :(
Environment
OS: Windows 10
Browser: Internet Explorer
Browser version: 11
Browser Driver version: 3.14.0.0 (64-bit)
Language Bindings version: NodeJS
The text was updated successfully, but these errors were encountered: