[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

HTTPS redirects to HTTP for monitoring

Subject: HTTPS redirects to HTTP for monitoring
From: wwaites at tardis.ed.ac.uk (William Waites)
Date: Sun, 18 Jan 2015 18:31:19 +0000 (GMT)
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]>

On 18 Jan 2015 18:15:09 -0000, "John Levine" <johnl at iecc.com> said:

    > I expect your users would fire you when they found you'd blocked
    > access to Google.

Doesn't goog do certificate pinning anyways, at least in their web
browser?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20150118/ffe7d3f8/attachment.pgp>

Follow-Ups:
- HTTPS redirects to HTTP for monitoring
  - From: Kelly.Setzer at wnco.com (Kelly Setzer)
- HTTPS redirects to HTTP for monitoring
  - From: damian at google.com (Damian Menscher)

References:
- HTTPS redirects to HTTP for monitoring
  - From: nanog at jack.fr.eu.org (nanog at jack.fr.eu.org)
- HTTPS redirects to HTTP for monitoring
  - From: johnl at iecc.com (John Levine)

Prev by Date: HTTPS redirects to HTTP for monitoring
Next by Date: HTTPS redirects to HTTP for monitoring
Previous by thread: HTTPS redirects to HTTP for monitoring
Next by thread: HTTPS redirects to HTTP for monitoring
Index(es):
- Date
- Thread