13:31:17.032 Received SSL connection from '/192.168.82.72:59211' to '/192.168.82.221:8443' 13:31:17.040 Document entered Communications Layer 13:31:17.040 Received an HTTP request: Protocol: HTTP/1.1 Scheme: https Method: PUT Client: 192.168.82.72 Request URL: https://s3.fssupport.com:8443/fs-sup-test1/test5.txt Listener Policy: HTTPS_8443 Virtual Directory: S3 Virtual Directory Virtual path: /* Auth Type: Cookies: Header Info: User-Agent: Crosscheck Networks SOAPSonar Content-Type: text/plain Authorization: ******** Host: s3.fssupport.com:8443 Content-Length: 5 Connection: keep-alive 13:31:17.040 Processing request for 'REST Policy: 'S3_SAMPLE'' 13:31:17.040 Authenticating basic auth credentials with acl 'FS_LDAP' 13:31:17.040 Authenticating using 'Group Policy: 'LDAP-FS_Online_LDAP'' 13:31:17.041 Found user 'newton' in cache for 'LDAP Policy: 'FS_Online_LDAP'' 13:31:17.041 Succeeded to authenticate user 'newton' using 'LDAP Policy: 'FS_Online_LDAP'' 13:31:17.041 Basic auth succeeded - User 'newton' has correct credentials 13:31:17.041 ACL check skipped - no ACL associated with network policy 'HTTPS_8443' 13:31:17.041 ACL check succeeded - User 'newton' allowed access by ACL 'FS_LDAP' 13:31:17.041 Message type filter match succeeded - matched filter 'REST (CRUD)' of type Simple 13:31:17.041 Reading a document of 5 bytes 13:31:17.041 Read succeeded 13:31:17.041 Request document: TEST5 13:31:17.041 Processing task list group for Content Policy Request 13:31:17.041 No task list group configured, document will not be processed 13:31:17.041 Processing task list group for Virtual Directory Request 13:31:17.041 No task list group configured, document will not be processed 13:31:17.042 S3 string to sign: PUT??text/plain?Tue, 13 Dec 2016 21:31:17 UTC?x-amz-meta-content-length:5?/fs-sup-test1/test5.txt 13:31:17.042 SSL handshake completed from '/192.168.82.72:59211' to '/192.168.82.221:8443' using protocol 'TLSv1.2', cipher suite 'TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256' and session id '58506721...8F52C756' 13:31:17.043 Connecting to back end server at URL 'https://fs-sup-test1.s3.amazonaws.com:443/test5.txt' 13:31:17.043 Stored header suppressed from proxying - Authorization: ******** 13:31:17.043 Stored header suppressed from proxying - host: s3.fssupport.com:8443 13:31:17.043 Stored header suppressed from proxying - connection: keep-alive 13:31:17.043 Stored header suppressed from proxying - content-length: 5 13:31:17.043 Adding Via header to request 13:31:17.244 No CRL policies have been specified, assuming not revoked. 13:31:17.244 No CRL policies have been specified, assuming not revoked. 13:31:17.244 Certificate chain DNs: 1. Subject DN: CN=*.s3.amazonaws.com, O=Amazon.com Inc., L=Seattle, ST=Washington, C=US Issuer DN: CN=DigiCert Baltimore CA-2 G2, OU=www.digicert.com, O=DigiCert Inc, C=US 2. Subject DN: CN=DigiCert Baltimore CA-2 G2, OU=www.digicert.com, O=DigiCert Inc, C=US Issuer DN: CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE 3. Subject DN: CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE Issuer DN: CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE 13:31:17.244 Server certificate chain check succeeded 13:31:17.306 Sending remote server a processed request: Method: PUT Remote IP: fs-sup-test1.s3.amazonaws.com Remote Port: 443 Remote Path: https://fs-sup-test1.s3.amazonaws.com:443/test5.txt Header Info: User-Agent: Forum Systems Content-Type: text/plain Date: Tue, 13 Dec 2016 21:31:17 UTC x-amz-meta-content-length: 5 Via: HTTP/1.1 192.168.82.221:8443 Authorization: ******** Message Body: Q#12$Q��~����2�xȺ�Q�]�#12�#4"���2�N���N[�B`��7�"��"���Y#19-}n1c ���#1dR�#11�#15�����p�E��-EX#4��v5��6�����t�)�k��#c�5޽�»�#13;�F��+�J�b]h�j #8�1˞�P�4Hw+ߐ�t� ЏGŁ`���Q#5���Y�\��Kͨ�#f$F1�R�����#cÊ�<��#bΉnլu��6�#1$G?*#1dD��L#8�U�#1a{#14#1b ����-/���u�#5#V#1e#7�8��w�W�#eъW�t<�9-���&�#3<$yI�������16'�?�g3ۢ�� 13:31:17.428 Received an HTTP response: Protocol: HTTP/1.1 Response Code: 200 Response Message: OK Remote Policy: S3RemotePolicy Remote URL: https://fs-sup-test1.s3.amazonaws.com:443/test5.txt Header Info: x-amz-id-2: q9R4Dofu82ll7Us/TNlyDhw5M2+mLP3TWzLE7Ed25gEZhjOFqaXiHiMaTDQbznl0h/O/r8Q9k4Q= x-amz-request-id: 7FD783861EA09E86 Date: Tue, 13 Dec 2016 21:31:18 GMT ETag: "998b2cb1738b8088bc7ec3a91cd03558" Content-Length: 0 Server: AmazonS3 13:31:17.428 Message type filter match succeeded - matched filter 'REST (CRUD)' of type Simple 13:31:17.428 Reading a document of 0 bytes 13:31:17.428 Read succeeded 13:31:17.428 Response document: 13:31:17.428 Processing task list group for Content Policy Response 13:31:17.428 No task list group configured, document will not be processed 13:31:17.428 Processing task list group for Virtual Directory Response 13:31:17.428 No task list group configured, document will not be processed 13:31:17.428 Stored header suppressed from proxying - Authorization: ******** 13:31:17.428 Stored header suppressed from proxying - content-length: 0 13:31:17.428 Adding Via header to response 13:31:17.429 Sending client a processed response: Status Code: 200 Header Info: x-amz-id-2: q9R4Dofu82ll7Us/TNlyDhw5M2+mLP3TWzLE7Ed25gEZhjOFqaXiHiMaTDQbznl0h/O/r8Q9k4Q= x-amz-request-id: 7FD783861EA09E86 Date: Tue, 13 Dec 2016 21:31:18 GMT ETag: "998b2cb1738b8088bc7ec3a91cd03558" Server: AmazonS3 Via: HTTP/1.1 192.168.82.221:8443 Message Body: 13:31:17.429 Document left Communications Layer