<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
I don’t know what “new Windows 8 APIs” you’re referring to. No APIs have been added-- the APIs I’m describing have existed since IE5.<br> <BR><div><div id="SkyDrivePlaceholder"></div>> Date: Thu, 8 Mar 2012 08:23:08 -0800<br>> From: pde@eff.org<br>> To: gauravkale@vista.aero<br>> CC: https-everywhere@eff.org<br>> Subject: Re: [HTTPS-Everywhere] HTTPS Everywhere for Internet Explorer<br>> <br>> These new Windows 8 APIs look superficially promising. What we should check:<br>> <br>> - Does this callback cover all of the possible request types? (Not just<br>> navigation but XML HTTP Requests and other things loaded from JS, favicons,<br>> etc)<br>> <br>> - Can we modify the request once we have a callback about it, in such away<br>> that the original requesting code gets the response from the https request?<br>> <br>> On Thu, Mar 08, 2012 at 10:39:56AM +0530, Gaurav . wrote:<br>> > <br>> > I’m not sure what "secure request rewriting" feature you mean here, but for IE, it’s absolutely possible for a BHO to rewrite a navigation URL from HTTP to HTTPS if it wants. The OnBeforeNavigate2 event is the one typically used for that purpose. <br>> <br>> > _______________________________________________<br>> > HTTPS-everywhere mailing list<br>> > HTTPS-everywhere@mail1.eff.org<br>> > https://mail1.eff.org/mailman/listinfo/https-everywhere<br>> <br>> <br>> -- <br>> Peter Eckersley pde@eff.org<br>> Technology Projects Director Tel +1 415 436 9333 x131<br>> Electronic Frontier Foundation Fax +1 415 436 9993<br></div> </div></body>
</html>