W3C home > Mailing lists > Public > public-xg-webid@w3.org > February 2011

RE: WebID-ISSUE-28 (bblfish): How does the WebID protocol (foaf+ssl) interact with TLS proxies [User Interface/Browsers]

From: peter williams <home_pw@msn.com>
Date: Sat, 12 Feb 2011 10:56:49 -0800
Message-ID: <SNT143-ds94F65ACE5209DF047BECF92EE0@phx.gbl>
To: "'WebID Incubator Group WG'" <public-xg-webid@w3.org>
Here is an example

http://www.microsoft.com/global/forefront/threat-management-gateway/en/us/Pu
blishingImages/diag-tmg-https-lg.jpg

from:

http://www.microsoft.com/forefront/threat-management-gateway/en/us/features.
aspx

-----Original Message-----
From: public-xg-webid-request@w3.org [mailto:public-xg-webid-request@w3.org]
On Behalf Of Yngve N. Pettersen (Developer Opera Software ASA)
Sent: Saturday, February 12, 2011 9:44 AM
To: WebID Incubator Group WG
Subject: Re: WebID-ISSUE-28 (bblfish): How does the WebID protocol
(foaf+ssl) interact with TLS proxies [User Interface/Browsers]



> C. Technical
>
>     How do TLS web proxies work? Which RFC are they based on?
>     How does it compare to tunnelling?

Assuming MITM proxy: They have to act like a normal TLS server, present a  
certificate that the client will accept, including a matching hostname for  
the origin server it is pretending to be. Normally these are generated on  
the fly by the proxy, signed by a local CA Root installed in the client.  
The MITM will usually process each HTTP request and response itself before  
passing it along to the intended recipient, perhaps modifying them before  
passing it on.
Received on Saturday, 12 February 2011 18:57:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:22 UTC