X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
References: <195047 DOT 70045 DOT qm AT web28316 DOT mail DOT ukl DOT yahoo DOT com>  <19001016 DOT post AT talk DOT nabble DOT com> <BLU113-W53371437F645339068C0ABE6D0 AT phx DOT gbl>
Subject: RE: Can't find how to fetch from the web
Date: Fri, 15 Aug 2008 19:24:44 +0100
Message-ID: <00c701c8ff04$30f3df60$9601a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <BLU113-W53371437F645339068C0ABE6D0@phx.gbl>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Mike Marchywka wrote on 15 August 2008 17:56:

> btw, is there a known problem with lynx that causes it to die when the
> url is too long? 

  There have been such problems in the past; I notice that the distro
version we have is 2.8.5rel5, and there have been two buffer overflows fixed
upstream since then, according to the CHANGES file.

> I don't have an example right now but I've noticed several times, and it
> appears to be with long urls, that lynx dies for no obvious reason. 

  Next time it happens, please keep a note of the URL and I'll look into it
if you like.  Any stackdumps you have lying around might be useful as well.
(Feel free to contact me offlist about this if you're concerned with
security.)

> I use something
> like lynx -dump -width 1200 url. I don't think this normally violates the
> command line length constraint which I thought was many k.

  No, it doesn't, and even if it did, you ought to just get an error from
bash, not a crash.

> Is there a
> server response that can provoke an abnormal termination ( want to say  
> seg fault or access violation but can't remember)?

  Absolutely not!  Why on earth would anyone want to let a remote server
crash their software?  No, you just get a nice friendly error status code
(e.g. 404) which your browser is supposed to display to you.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/