huseyincengiz adlı üyeden alıntı: mesajı görüntüle
3proxy notlarında mevcut, ama teknik olarak sunucunun ssl bilgisi araya girme olayını bilmiyorum. aynı şeyden mi bahsediyoruz bilmiyorum. Atıyorum proxy url'de https://instagram.com olarak yazılıyor ve sonuç 200 ok döndürüyor. Konudaki ekran görüntüsünde gönderdim
+ HTTPS (CONNECT) proxy (compatible with HTTP/2 / SPDY)
Yeniden selamlar,
bahsettigim şey şu; aşağıda yer alan satırlardaki bazı yerleri bold olarak işaretledim.
Bu örnek Kullanıcının SSL bilgisi ile ilerliyor. Bu sebeple 100 kullanıcı gönderirseniz hepsinin SSL bilgisi aynı olduğu için patlar


* Rebuilt URL to: https://www.instagram.com/
* Trying 96.66.103.123...
* TCP_NODELAY set
* Connected to 96.66.103.123 (96.66.103.123) port 8080 (#0)
* Establish HTTP proxy tunnel to www.instagram.com:443
> CONNECT www.instagram.com:443 HTTP/1.1
> Host: www.instagram.com:443
> User-Agent: curl/7.54.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 OK
<
* Proxy replied OK to CONNECT request
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@ STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=US; ST=California; L=Menlo Park; O=Facebook, Inc.; CN=*.www.instagram.com
* start date: Sep 5 00:00:00 2018 GMT
* expire date: Dec 12 12:00:00 2019 GMT
* subjectAltName: host "www.instagram.com" matched cert's "www.instagram.com"
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
* SSL certificate verify ok.
* 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 0x7ff688002000)
> GET / HTTP/2
> Host: www.instagram.com
> User-Agent: curl/7.54.0
> Accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 200
< content-type: text/html; charset=utf-8
< cache-control: private, no-cache, no-store, must-revalidate
< pragma: no-cache
< expires: Sat, 01 Jan 2000 00:00:00 GMT
< vary: Accept-Language, Cookie, Accept-Encoding
< content-language: en
< date: Fri, 19 Oct 2018 16:14:00 GMT
< content-length: 25457
< strict-transport-security: max-age=60
< x-frame-options: SAMEORIGIN