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
Using res.end() to write result instead of res.write() followed by
res.end() will cause node not to use chunked encoding and include
Content-Length header. (See nodejs/node#26005) This small distinction is
important with some client. For example, Windows 10's MDM enrollment
system will not accept chunked response
(https://docs.microsoft.com/en-us/windows/client-management/mdm/on-premise-authentication-device-enrollment).
This might improve compatibility with some other clients, too. However,
there's a small chance that some client may expect the response to be
chunked. So, I put this behind an option which defaults to enabled and
can be disabled if needed.
Copy file name to clipboardExpand all lines: Readme.md
+1
Original file line number
Diff line number
Diff line change
@@ -219,6 +219,7 @@ Server options include the below:
219
219
-`ca`: An array of strings or Buffers of trusted certificates in PEM format. If this is omitted several well known "root" CAs will be used, like VeriSign. These are used to authorize connections.
220
220
-`crl` : Either a string or list of strings of PEM encoded CRLs (Certificate Revocation List)
221
221
-`ciphers`: A string describing the ciphers to use or exclude, separated by :. The default cipher suite is:
222
+
-`enableChunkedEncoding`: A boolean for controlling chunked transfer encoding in response. Some client (such as Windows 10's MDM enrollment SOAP client) is sensitive to transfer-encoding mode and can't accept chunked response. This option let user disable chunked transfer encoding for such a client. Default to `true` for backward compatibility.
222
223
223
224
```javascript
224
225
var xml =require('fs').readFileSync('myservice.wsdl', 'utf8');
0 commit comments