Currently, new-run-webkit-websocketserver ignores TLS related arguments, -k and -c. Also we need to support --ca-certificate for client certificate authentication.
Created attachment 147522 [details] Patch
Comment on attachment 147522 [details] Patch LGTM. We don't need to modify NRWT?
Currently, I have no plan to use this feature from usual layout tests on NRWT. In the case of Chromium port, we use new-run-webkit-websocketserver from some unit tests. This is my major motivation to modify new-run-webkit-websocketserver now. Also this change will help some new client certificate layout tests in the future.
(In reply to comment #3) > Currently, I have no plan to use this feature from usual layout tests on NRWT. > In the case of Chromium port, we use new-run-webkit-websocketserver from some unit tests. > This is my major motivation to modify new-run-webkit-websocketserver now. > Also this change will help some new client certificate layout tests in the future. I see. Thank you for explanation :)
Comment on attachment 147522 [details] Patch looks fine.
Comment on attachment 147522 [details] Patch Clearing flags on attachment: 147522 Committed r120342: <http://trac.webkit.org/changeset/120342>
All reviewed patches have been landed. Closing bug.