severity 352255 wishlist
retitle 352255 Not enough technical detail in network error message
thanks

Unfortunately that sort of terminology tends to confuse rather than
help the vast majority of users.

* Jan-Benedict Glaw ([EMAIL PROTECTED]) wrote:
> On Fri, 2006-02-10 21:07:55 +0100, Mike Hommey <[EMAIL PROTECTED]> wrote:
> > On Fri, Feb 10, 2006 at 06:58:59PM +0100, Jan-Benedict Glaw <[EMAIL 
> > PROTECTED]> wrote:
> > > Package: firefox
> > > Architecture: i386
> > > Version: 1.5.dfsg+1.5.0.1-2
> > > Distribution: unstable/sid
> > > 
> > > Hi!
> > > 
> > > If you open a web site whose HTTP server isn't running, or after
> > > different types of network errors, the displayed error message isn't
> > > really helpful.  M$ Internet Explorer may display "Some kind of error
> > > has appeared", but from Firefox, I actually expect something more
> > > helpful, like libc's strerror() output for transport errors or
> > > something like that.
> > 
> > How the following message can not be enough ?
> 
> "While trying to connect() to foo.bar.com, the connect timed out."
> ...or, if the socket was set to non-blocking mode:
> "While trying to connect() to foo.bar.com, the connect was aborted
>  after waiting 2000msec."
> "While trying to connect() to foo.bar.com, the connection was
> refused."
> 
> ...
> 
> > Firefox can't establish a connection to the server at localhost.
> > 
> >     *   The site could be temporarily unavailable or too busy. Try again in 
> > a few
> >           moments.
> 
> Is this a locally generated timeout? ...or a RST because of a full SYN
> queue?
> 
> >     *   If you are unable to load any pages, check your computer's network
> >           connection.
> 
> I don't like poking around for a reason, but rather get the errno
> value of whatever libc call actually failed.
> 
> >     *   If your computer or network is protected by a firewall or proxy, 
> > make sure
> >           that Firefox is permitted to access the Web.
> 
> The point is that there are basically two things to debug a
> non-working connection: strace firefox (which isn't a really nice
> thing to look at) or tcpdump the network.
> 
> So if Firefox would just print out the libc error that occured, it
> would probably save the user from needing to go down into the details.
> 
> Thanks,
>       Jan-Benedict
> 



-- 
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]
1024D/16D970C6 097C 4861 9934 27A0 8E1C  2B0A 61E9 8ECF 16D9 70C6

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ 
O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ 
G e h! r- y+ 
------END GEEK CODE BLOCK------

Attachment: signature.asc
Description: Digital signature

Reply via email to