AWS SDK不容連接背後的企業代理

Question

我的工作站的背後是企業的代理，我已經設置環境變量，我能夠使用的一切，但AWS-SDK和的NodeJS。在這裏，TCP連接的轉儲：

No.  Time   Source    Destination   Protocol Length Info 
    2 1.834143  105.103.15.106  105.103.82.47   TCP  74  54952 → 8080 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=497254718 TSecr=0 WS=128 
    3 1.836141  105.103.82.47   105.103.15.106  TCP  74  8080 → 54952 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 SACK_PERM=1 TSval=3399116010 TSecr=497254718 WS=128 
    4 1.836165  105.103.15.106  105.103.82.47   TCP  66  54952 → 8080 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=497254719 TSecr=3399116010 
    5 1.836779  105.103.15.106  105.103.82.47   TCP  310 54952 → 8080 [PSH, ACK] Seq=1 Ack=1 Win=29312 Len=244 TSval=497254719 TSecr=3399116010 
    6 1.838250  105.103.82.47   105.103.15.106  TCP  66  8080 → 54952 [ACK] Seq=1 Ack=245 Win=15616 Len=0 TSval=3399116012 TSecr=497254719 
20 123.670911  105.103.82.47   105.103.15.106  TCP  66  8080 → 54952 [FIN, ACK] Seq=1 Ack=245 Win=15616 Len=0 TSval=3399237839 TSecr=497254719 
21 123.674168  105.103.15.106  105.103.82.47   TCP  66  54952 → 8080 [FIN, ACK] Seq=245 Ack=2 Win=29312 Len=0 TSval=497285178 TSecr=3399237839 
22 123.676592  105.103.82.47   105.103.15.106  TCP  66  8080 → 54952 [ACK] Seq=2 Ack=246 Win=15616 Len=0 TSval=3399237843 TSecr=497285178 

注意，三次握手去確定，比客戶端（IP上106結束）發送關於包號碼5的一些數據（PSH，ACK），並立即，receiveis proxy' s ACK（包號6）。那麼很長一段時間沒有通信（7到19之間的包不是來自此tcp會話），數據包20是FIN（由於沒有發送包而導致的代理超時？）。此會話由example provided by Amazon生成。

節點版本：在6.10.0，6.11.0和8.1.3 SDK安裝今日（2.82.0）

作爲對比測試，我運行相同的Ubuntu的機器上aws cloudformatin describe-stack-resources --stack-name my-stack。如已知的，aws CLI是蟒，命令運行確定，會話是這樣：

No.  Time   Source    Destination   Protocol Length Info 
    1 0.000000  105.103.15.106  105.103.82.47   TCP  74  54940 → 8080 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=496906305 TSecr=0 WS=128 
    2 0.001987  105.103.82.47   105.103.15.106  TCP  74  8080 → 54940 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 SACK_PERM=1 TSval=3397722434 TSecr=496906305 WS=128 
    3 0.002008  105.103.15.106  105.103.82.47   TCP  66  54940 → 8080 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=496906305 TSecr=3397722434 
    4 0.002100  105.103.15.106  105.103.82.47   TCP  127 [TCP segment of a reassembled PDU] 
    5 0.003967  105.103.82.47   105.103.15.106  TCP  66  8080 → 54940 [ACK] Seq=1 Ack=62 Win=14592 Len=0 TSval=3397722436 TSecr=496906306 
    6 0.003974  105.103.15.106  105.103.82.47   HTTP  68  CONNECT cloudformation.us-east-1.amazonaws.com:443 HTTP/1.0 
    7 0.006035  105.103.82.47   105.103.15.106  TCP  66  8080 → 54940 [ACK] Seq=1 Ack=64 Win=14592 Len=0 TSval=3397722438 TSecr=496906306 
    8 0.247802  105.103.82.47   105.103.15.106  HTTP  185 HTTP/1.0 200 Connection established 
    9 0.247810  105.103.15.106  105.103.82.47   TCP  66  54940 → 8080 [ACK] Seq=64 Ack=120 Win=29312 Len=0 TSval=496906367 TSecr=3397722681 
10 0.248938  105.103.15.106  105.103.82.47   TLSv1.2 583 Client Hello 
11 0.250985  105.103.82.47   105.103.15.106  TCP  66  8080 → 54940 [ACK] Seq=120 Ack=581 Win=15616 Len=0 TSval=3397722683 TSecr=496906367 
12 0.684003  105.103.82.47   105.103.15.106  TLSv1.2 1995 Server Hello 
13 0.684011  105.103.15.106  105.103.82.47   TCP  66  54940 → 8080 [ACK] Seq=581 Ack=2049 Win=33152 Len=0 TSval=496906476 TSecr=3397723117 
14 0.690001  105.103.82.47   105.103.15.106  TLSv1.2 1488 CertificateServer Key Exchange, Server Hello Done 
15 0.690866  105.103.15.106  105.103.82.47   TLSv1.2 216 Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message 
16 0.692974  105.103.82.47   105.103.15.106  TCP  66  8080 → 54940 [ACK] Seq=3471 Ack=731 Win=16640 Len=0 TSval=3397723125 TSecr=496906478 
17 0.968807  105.103.82.47   105.103.15.106  TLSv1.2 141 Change Cipher Spec, Encrypted Handshake Message 
18 0.969476  105.103.15.106  105.103.82.47   TLSv1.2 679 Application Data 
19 0.970992  105.103.82.47   105.103.15.106  TCP  66  8080 → 54940 [ACK] Seq=3546 Ack=1344 Win=17920 Len=0 TSval=3397723403 TSecr=496906547 
20 1.319977  105.103.82.47   105.103.15.106  TLSv1.2 617 Application Data 
21 1.324998  105.103.82.47   105.103.15.106  TCP  2114 [TCP segment of a reassembled PDU] 
22 1.325003  105.103.15.106  105.103.82.47   TCP  66  54940 → 8080 [ACK] Seq=1344 Ack=6145 Win=43008 Len=0 TSval=496906636 TSecr=3397723753 
23 1.329979  105.103.82.47   105.103.15.106  TLSv1.2 133 Application Data 
24 1.332987  105.103.15.106  105.103.82.47   TCP  66  54940 → 8080 [FIN, ACK] Seq=1344 Ack=6212 Win=43008 Len=0 TSval=496906638 TSecr=3397723763 
25 1.373825  105.103.82.47   105.103.15.106  TCP  66  8080 → 54940 [ACK] Seq=6212 Ack=1345 Win=17920 Len=0 TSval=3397723807 TSecr=496906638 
26 1.606041  105.103.82.47   105.103.15.106  TLSv1.2 119 Encrypted Alert 
27 1.606063  105.103.15.106  105.103.82.47   TCP  54  54940 → 8080 [RST] Seq=1345 Win=0 Len=0 

注意，從1至3的數據包是三方握手和完全相同的與JS SDK，分組4是類似於分組5的JS SDK，它沒有在摘要中顯示，但它也有PSH標誌和ACK，不同之處在於內容（預期），數據包5是代理對該數據的ACK。從東西這一點上是不同的，aws CLI接收到的數據之後，一旦ACK到達上包6.發送下一個包，aws CLI發送FIN，ACK接收，加密警報和發送RST（這不是預期由於加密警報） 。

我不能找到爲什麼JS SDK停止最後一個服務器的ACK後發送數據。但由於代理超時，過一段時間後發送FIN ACK，我的節點腳本似乎長掛起，直至中止與以下錯誤：

{ NetworkingError: socket hang up 
at TLSSocket.onHangUp (_tls_wrap.js:1124:19) 
at TLSSocket.g (events.js:292:16) 
at emitNone (events.js:91:20) 
at TLSSocket.emit (events.js:185:7) 
at endReadableNT (_stream_readable.js:974:12) 
at _combinedTickCallback (internal/process/next_tick.js:80:11) 
at process._tickDomainCallback (internal/process/next_tick.js:128:9) 

消息：「套接字掛斷」， 代碼：「NetworkingError」， 區域：'us-west-2'， hostname：'bucket.s3-us-west-2.amazonaws.com'， retryable：true， time：2017-07-07T19：31：29.494Z} null

任何線索？

Answer 1

縱觀輸出，CLI的連接使用CONNECT描述here，而你的SDK的NodeJS調用不會出現（HTTP隧道）將這樣做。看起來，帶有CONNECT類型代理的NodeJS SDK有點奇怪。我建議你找過其中提到使用node-tunnel給像這樣的bug on it：

var AWS = require('aws-sdk'); 
var tunnel = require('tunnel'); 

var tunnelingAgent = tunnel.httpsOverHttp({ 
    proxy: { // Proxy settings 
    host: 'proxyhost', 
    port: 8080, 
    proxyAuth: "user:pass", 
    } 
}); 

AWS.config.update({ 
    httpOptions: { 
    agent: tunnelingAgent 
    } 
}); 

var s3 = new AWS.S3({region: 'us-west-2'}); 
s3.getObject({Bucket: 'bucket', Key: 'key'}, function (err, data) { 
    console.log(err, data); 
}); 

雖然我很遺憾沒有環境設置來測試此我希望這將至少給你如何開始解決這個問題。