From owner-freebsd-questions@FreeBSD.ORG Fri Apr 3 07:32:56 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7F8FA2C7 for ; Fri, 3 Apr 2015 07:32:56 +0000 (UTC) Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E876F4C for ; Fri, 3 Apr 2015 07:32:56 +0000 (UTC) Received: by obbec2 with SMTP id ec2so161149872obb.3 for ; Fri, 03 Apr 2015 00:32:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=5rcm/lmzUaRYvqXGW0v3aeZY+XVh9MK6kUBjaYlzd+c=; b=rHRZ/xR3rBzcUqKIVVS7TIwTFaATtA9a7gsM9MEe5zAyYlCO0+QO2EtW+BJWOUeJRK A0+Md+Hx+f6PwsLkSMEHqpMzBsxGC8v7Ue/f2Tt0FsRVwgDbpbUfsUttnQl/gsH1ZiXB dX7/D7Pfx5g57fk/Ikw3c+14S+ZRM80mzyA3sdhdxRhnO9kj/kBGHAC9JCVvfG1mOanV CgFcHL6QYSCPFZ4Oxns9wE7Iw2iC/Jw7PX0UgDrjVHynWdm+Zhy2mh1YjU2wZc3A84MC aGQ4h+YTGkrhWe0Nys6PHcWfXH33/bwcZd5jKX9YvDJmx21Z7cpA299Kp15YVYPvSfJe QT1A== X-Received: by 10.60.133.176 with SMTP id pd16mr1470559oeb.78.1428046375555; Fri, 03 Apr 2015 00:32:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.115.73 with HTTP; Fri, 3 Apr 2015 00:32:35 -0700 (PDT) In-Reply-To: <551DC4F7.5090005@gmail.com> References: <551DA84D.8030205@gmail.com> <20150402222539.37e330f8@gumby.homeunix.com> <551DC4F7.5090005@gmail.com> From: Nino J Date: Fri, 3 Apr 2015 09:32:35 +0200 Message-ID: Subject: Re: Why does FreeBSD insist on https? To: User Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2015 07:32:56 -0000 On Fri, Apr 3, 2015 at 12:38 AM, jd1008 wrote: > On 04/02/2015 03:25 PM, RW wrote: > >> On Thu, 02 Apr 2015 14:36:29 -0600 >> jd1008 wrote: >> >>> https prevents intermediate hop points (such as your isp) >>> from looking at the page content, or at the terms of your >>> search. But that does not prevent them from seeing the url. >>> >> Actually it does. The url is sent inside the encryption. >> > That is good to know. I had thought otherwise. Just bear in mind that the OP mentioned redirect to https. That means that the initial request to the exact URL (i.e. before being redirected and switching to https) is visible. -- Nino