Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<3E3057F8.8071EAC1@wapme-systems.de>
Date:	Thu, 23 Jan 2003 22:00:40 +0100
From:	Stipe Tolj <tolj AT wapme-systems DOT de>
Organization:	Wapme Systems AG
X-Accept-Language:	de
MIME-Version:	1.0
To:	kouno_tetsu AT artiza DOT co DOT jp
CC:	cygwin AT cygwin DOT com
Subject:	Re: Apache corrupt big file
References:	<GEEHDGCXV2VZWIH614XCLZYHD9PK DOT 3e300606 AT 067kohno2>

Tetsu KOUNO wrote:
> 
> I tried FTP(cygwin inetutils) download for the same file, it was successful.
> I think it means Cygwin APIs are okay even with my environment.
> It seems Apache specific issue...
> Any updates on this issue?

no, but that's not an adequate statement.

I know that FTP (and even SSH's scp) work. Apache does a lot more
thatn FTP or SSH, terms of socket connection pool re-use etc. So this
result is not an implication to your direction.

But why does the *same* Apache code run on 1.3.10-2 without any
problems?!

Stipe

tolj AT wapme-systems DOT de
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info AT wapme-systems DOT de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -