Huachao Mao comments

Results 140 comments of


                                            Huachao Mao

write EPROTO 11416:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:d:\_vsts\3\s\vendor\node\deps\openssl\openssl\ssl\record\ssl3_record.c:252:

@cb3mass It seems the https request uses the incorrect TLS version

Using NTLM authentication

@symbioticKid , thanks for your suggestion. And I think this is not a quite general requirement, so I'd like to put this in backlog.

@Yvand I know your pain. Currently we use [Request package](https://www.npmjs.com/package/request) to issue HTTP request, which doesn't have native NTLM support, although it already some related feature discussions like [NTLM Support](https://github.com/request/request/issues/808)...

Using NTLM authentication

@brbecker my extension has migrated to [got library](https://www.npmjs.com/package/got) for several releases

Add more logging

@MisinformedDNA nice suggestion, I will consider this carefully.

XPath with namespace in request variable usage is not supported

@ZefQ @betancour nice workaround.

XPath with namespace in request variable usage is not supported

@Stadly sure, I will leave this issue open

the variable value is incorrect when I use named request to get value of Long data type from response body

@terryliulj you are right, since the number is larger than the maximum number `2 ^ 53 - 1`, and the native `JSON.parse` doesn't work as expected. I am still considering...

Send all requests in a file

@bm-stschneider do you mean just run all the requests in the correct order and display all the responses

Send all requests in a file

> was this implemented? @ricmrodrigues No, it wasn't.