- From: Simon Pieters <simonp@opera.com>
- Date: Thu, 08 Aug 2013 13:38:55 +0200
- To: "'Anne van Kesteren'" <annevk@annevk.nl>, "Nilsson, Claes1" <Claes1.Nilsson@sonymobile.com>
- Cc: "Jonas Sicking" <jonas@sicking.cc>, "www-dom@w3.org" <www-dom@w3.org>, "public-sysapps@w3.org" <public-sysapps@w3.org>
On Thu, 08 Aug 2013 13:05:07 +0200, Nilsson, Claes1
<Claes1.Nilsson@sonymobile.com> wrote:
> This is not just for debugging. Looking at the example I give in the
> mail, i.e. when the attempt to create a TCP socket fails I expect the
> web application to handle each error situation ("no network
> contact","peer does not respond", "local address/port pair is already in
> use") differently.
Usually we don't expose why a network connection fails to scripts in order
to not reveal information behind the user's firewall to attackers.
--
Simon Pieters
Opera Software
Received on Thursday, 8 August 2013 11:34:18 UTC