I need to take that back.  It looks like modern implementations of HTTPS send normal HTTP (headers, body and all) over an encrypted connection and this *would* protect the requested URLs.  The only thing a man-in-the-middle would know is that a connection has been made and possibly how many bytes of encrypted data had been sent/received.<div>

<br></div><div>It looks like I need to send an email to my Internet Programming professor.  ;) </div><div><br></div><div>-Aaron<br><br><div class="gmail_quote">On Mon, Oct 3, 2011 at 3:44 PM, Steven Walling <span dir="ltr">&lt;<a href="mailto:swalling@wikimedia.org">swalling@wikimedia.org</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Mon, Oct 3, 2011 at 3:13 PM, Aaron Halfaker <span dir="ltr">&lt;<a href="mailto:aaron.halfaker@gmail.com" target="_blank">aaron.halfaker@gmail.com</a>&gt;</span> wrote:<br>

<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<p>HTTPS doesn&#39;t hide the URL of the pages you visit.  Instead it hides the content of the page you requested (public) and the content you sent (public if it was an edit).  </p>
<p>-Aaron</p></blockquote></div></div>This is a good point, especially because I meant to send it to Communications Committee list, not RCOM. Too many committees in my contact list. ;)  <div><div></div><div class="h5"><br clear="all">

<div><br></div>-- <br>Steven Walling<div>

Community Organizer at Wikimedia Foundation</div><div><a href="http://wikimediafoundation.org" target="_blank">wikimediafoundation.org</a></div><br>
</div></div><br>_______________________________________________<br>
RCom-l mailing list<br>
<a href="mailto:RCom-l@lists.wikimedia.org">RCom-l@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/rcom-l" target="_blank">https://lists.wikimedia.org/mailman/listinfo/rcom-l</a><br>
<br></blockquote></div><br></div>