Heater741 Posted January 5, 2019 Posted January 5, 2019 Note: Unnecessary use of -X or --request, POST is already inferred. * Trying 91.134.1.104... * TCP_NODELAY set * Connected to http://www.digitalcombatsimulator.com (91.134.1.104) port 443 (#0) * PolarSSL: Connecting to http://www.digitalcombatsimulator.com:443 * ALPN, offering h2 * ALPN, offering http/1.1 * PolarSSL: Handshake complete, cipher is TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384 * Dumping cert info: * cert. version : 3 * serial number : 0E:53:62:7F:F0:CD:CE:A8:26:8D:74:73:D4:78:CD:78 * issuer name : C=US, O=DigiCert Inc, OU=www.digicert.com, CN=Thawte TLS RSA CA G1 * subject name : CN=*.digitalcombatsimulator.com * issued on : 2018-08-07 00:00:00 * expires on : 2019-01-28 12:00:00 * signed using : RSA with SHA-256 * RSA key size : 4096 bits * basic constraints : CA=false * subject alt name : *.digitalcombatsimulator.com, digitalcombatsimulator.com * key usage : Digital Signature, Key Encipherment * ext key usage : TLS Web Server Authentication, TLS Web Client Authentication * ALPN, server accepted to use h2 * SSL connected * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x1a31552b160) > POST /gameapi/crashreport/ HTTP/2 > Host: http://www.digitalcombatsimulator.com > User-Agent: curl/7.61.1 > Accept: */* > Content-Length: 1618862 > Content-Type: multipart/form-data; boundary=------------------------acafa72fff84545c > * Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
mia389 Posted January 8, 2019 Posted January 8, 2019 3 times tonight on multiplayer my game CTD when I crashed in huey. Inam running open beta and seems it’s happening after the last update
Shadow KT Posted January 8, 2019 Posted January 8, 2019 https://forums.eagle.ru/showthread.php?t=228182 'Shadow' Everybody gotta be offended and take it personally now-a-days
Recommended Posts