• [^] # Re: redirection HTTPS

    Posté par . En réponse à la dépêche ExaProxy, un proxy HTTP filtrant. Évalué à 3.

    En redirigant la premiere requete vers ce site

    c'est justement à ce moment que le navigateur va gueuler, car le proxy va lui présenter un certificat qui ne correspond pas à "nosslsearch.google.com", non ?

    je ne vois pas où le proxy s'insère dans la séquence suivante:

    curl -vvv "https://nosslsearch.google.com/"
* About to connect() to nosslsearch.google.com port 443 (#0)
* Trying 216.239.32.20... connected
* Connected to nosslsearch.google.com (216.239.32.20) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
 CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using RC4-SHA
* Server certificate:
* subject: C=US; ST=California; L=Mountain View; O=Google Inc; CN=*.google.com
* start date: 2012年02月16日 10:38:09 GMT
* expire date: 2013年02月16日 10:48:09 GMT
* subjectAltName: nosslsearch.google.com matched
* issuer: C=US; O=Google Inc; CN=Google Internet Authority
* SSL certificate verify ok.
> GET / HTTP/1.1
> User-Agent: curl/7.21.0
> Host: nosslsearch.google.com
> Accept: */*
>
< HTTP/1.1 302 Found
< Cache-Control: private
< Content-Type: text/html; charset=UTF-8
< Location: http://www.google.com
< Content-Length: 218
< Date: 2012年3月02日 00:04:41 GMT
< Server: GFE/2.0
<
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>302 Moved</TITLE></HEAD><BODY>
<H1>302 Moved</H1>
The document has moved
<A HREF="http://www.google.com">here</A>.
</BODY></HTML>
* Connection #0 to host nosslsearch.google.com left intact
* Closing connection #0