Re: HTTPS and URL encoding
From: Thor Kottelin (thor_at_anta.net)
Date: 05/28/04
- Next message: Barry Margolin: "Re: HTTPS and URL encoding"
- Previous message: Barry Margolin: "Re: HTTPS and URL encoding"
- In reply to: Barry Margolin: "Re: HTTPS and URL encoding"
- Next in thread: Barry Margolin: "Re: HTTPS and URL encoding"
- Reply: Barry Margolin: "Re: HTTPS and URL encoding"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 28 May 2004 01:23:27 +0300
Barry Margolin wrote:
>
> In article <40B64AD4.9C0A1C1A@anta.net>, Thor Kottelin <thor@anta.net>
> wrote:
> > Your ISP will see a TCP connection, an SSL/TLS handshake, and encrypted
> > stuff from there on. They might also see one or more preceding DNS queries,
> > which might give away the host name, which, in turn and OTOH, would probably
> > also be easy to determine by doing a reverse lookup.
>
> Not if it's a virtual server -- multiple names map to the same address,
> and the reverse lookup probably wouldn't produce the one that the user
> used.
It's not very common for HTTPS to be available on name-based virtual hosts,
is it?
Thor
-- http://thorweb.anta.net/ IRCnet #areena
- Next message: Barry Margolin: "Re: HTTPS and URL encoding"
- Previous message: Barry Margolin: "Re: HTTPS and URL encoding"
- In reply to: Barry Margolin: "Re: HTTPS and URL encoding"
- Next in thread: Barry Margolin: "Re: HTTPS and URL encoding"
- Reply: Barry Margolin: "Re: HTTPS and URL encoding"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]