httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fiedler Roman <Roman.Fied...@ait.ac.at>
Subject AW: [users@httpd] strange 32bit apache-problem
Date Mon, 15 Sep 2014 11:24:28 GMT
> Von: Hajo Locke [mailto:Hajo.Locke@gmx.de]
>
> Hello,
>
> Am 15.09.2014 um 11:57 schrieb Fiedler Roman:
> > Hi,
> >
> >> Von: Hajo Locke [mailto:Hajo.Locke@gmx.de]
> >>
> >> Hello,
> >>
> >> one of my machines i upgraded tu ubuntu 14.04 32bit.
> >> there is a apache 2.2.27 running on it (non ubuntu-repo).
> >> i have a textfile which is 512byte long, it contains just some chars,
> >> just one long line with a linebreak at the end.
> >>
> >> If i request this file by wget from the same machine, all is looking
> >> fine and readable.
> >> If i request this file from a other machine, then file seems to be
> >> corrupted. response-header and filesize are still ok. file contents
> >> looks like i would have requested some binary content.
> >> content looks like this (just first 8 bytes):
> >> ^@^@^@^@
> >>
> >> if i reduce length of line, then at a point file is ok again and
> >> readable. What could be the problem here?
> >> Other files with shorter lines are also ok. it seems to be special in
> >> here, that file is very long and only one linebreak at the end
> >> i have other machines which are upgraded the same way with same
> >> software, only difference is that they are 64bit machines and they are
> >> working without problems.
> >> Never had something like this, some other not upgraded 32bit machines
> >> still have no problem with original file.
> >>
> >> What to do now?
> > Did you look at it in an editor? If yes, editors might be tricky.
> >
> > Could you post xxd of original file, file retrieved locally and on remote
> > machine?
> >
> > Roman
> i used different editors, graphical or text. display is different, but
> in all cases corrupt.
> for testing i created a 512byte file containing a lot of a's
> i post xxd of files. first one is the file a.html retrieved from same
> machine which is ok:
>
> 0000000: 6161 6161 6161 6161 6161 6161 6161 6161  aaaaaaaaaaaaaaaa
> ..
> 00001f0: 6161 6161 6161 6161 6161 6161 6161 610a  aaaaaaaaaaaaaaa.
>
> now comes xxd of same file retrieved by an other client:
>
> 0000000: 0000 0000 0000 0000 0000 0000 0000 0000  ................
> ...
> 00001f0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
>
> it seems to work when line in file is exactly 255 byte long.  this
> retrieved file looks good. if i edit the file and add one more a then i
> get the rubbish at next request.
>
> Do you have an idea whats going wrong?

That's really strange. Are you delivering via port 80? If yes, you could do 
tcpdump of data leaving machine A and another dump on machine B of received 
data to see if data on wire is still correct.

Perhaps some IDS filtering out/replacing the content in between?

Mime
View raw message