From: <djnews@thedixons.com>
To: <pmcferrin@insight.rr.com>, <cygwin@cygwin.com>
Subject: Re: Apache 1.3.22 on cygwin under XP - loosing data
Date: Tue, 28 May 2002 04:01:00 -0000 [thread overview]
Message-ID: <000801c205c8$08f07690$bd7ba8c0@q6f3d6> (raw)
In-Reply-To: <3CF297BF.828BE2F@insight.rr.com>
I agree with what you found. I now can get it to fail on plain html text as
well.
It usually starts to corrupt bits at around the 32K point. I can pull up
hundreds
of thumbnails (~10-20K) without a problem. Out of hundreds of bigger
jpgs, 100% of the bad ones are >32K and 100% of the bad ones are <40K
(but it is not a clean break at 32K). Also, text htmls go bad around the
same
point. I have actually gotten it to pick up what looks like data from
another
file on disk! I have seen that behavior 3 or 4 times.
I have tried the httpd binary that came with the cygwin distribution as well
as the build you can link to on the "Software" page. They both fail.
I know they are the same revision (Apache/1.3.24 (cygwin)) but they are
wildly differrent sizes so I figured I'd try them both.
I have not yet download the win32 build at apache.org but I might try
that next.
-dan
----- Original Message -----
From: "Paul McFerrin" <pmcferrin@insight.rr.com>
To: "Dan Dixon" <dan@thedixons.com>; <cygwin@cygwin.com>
Sent: Monday, May 27, 2002 2:31 PM
Subject: Re: Apache 1.3.22 on cygwin under XP - loosing data
> Nice thought... I did verify that all of the mounts are binmode mounts.
>
> I saved one of the bad images that the browser downloaded and compared it
with the original
> file on disk. Here is what I've observed....
> - The two files (good & bad) were identical in size!
> - The bad file did contain some \n and \r but there were not adjacent.
>
> I did a "cmp good_file bad_file" and here is a partial output:
> 32769 172 0
> 32771 377 341
> 32772 0 303
> 32773 274 0
> 32774 333 0
> 32775 234 342
> 32776 204 303
> 32777 50 22
> 32778 262 0
> 32779 7 0
> 32780 146 0
> 32781 41 265
> ...
>
> As you can see, it is NOT a cr/nl problem. It looks like bits are getting
dropped. Another
> thing to note, I can purge my cache and reload the page. The reloaded
page is still screwey
> but NOT in an identical fashion. If it was a cr/nl problem, I would
expect it to be
> reproducable.
>
> -paul mcferrin
>
>
> Dan Dixon wrote:
> >
> > I have the same problem with the install I did tonight.
> > Just a guess, but you know what it looks like? It looks
> > like a text/binary mode issue. Any picture that has a cr/lf
> > in it will get trashed, but not every picture. I'm going to
> > write a perl script to check for this and see if it lines up
> > with the pictures that are getting trashed. Now I have
> > now idea how to fix this :)
> >
> > -dan
>
>
--
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/
next prev parent reply other threads:[~2002-05-27 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000501c20556$c66b43c0$bd7ba8c0@q6f3d6>
2002-05-28 2:32 ` Paul McFerrin
2002-05-28 4:01 ` djnews [this message]
[not found] ` <3CF2FD22.D8A5D3B9@insight.rr.com>
[not found] ` <000701c206dc$f66a7960$bd7ba8c0@q6f3d6>
2002-05-29 8:46 ` Paul McFerrin
2002-05-29 10:16 ` Jason Tishler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000801c205c8$08f07690$bd7ba8c0@q6f3d6' \
--to=djnews@thedixons.com \
--cc=cygwin@cygwin.com \
--cc=pmcferrin@insight.rr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).