no jpgs via http - https works fine (apache 1.3.34 and 2.2.3)

[Philipp Flesch]

Hi!
We are running an HP RX2600 Itanium Server with debian eth (kernel
2.6.18) for some local education projects.
Since we applied some updates (marked as non critical) via apt-get
upgrade we have got problems with some jpgs.

Loading the images via https everything works fine. Loading the images
via http we got into a loop without generating any error in the logs.
After resizing the picture with gimp the broken picture works fine.

We found out, that some broken pictures have got EXIF-headers with
camera information. Most of the pictures were uploaded months ago and
have already been displayed without any problems before the "patchday".

Please feel free to try out yourself:

apache 1.3.34
http://wvbg.bndlg.de/~max/apache vs. https://wvbg.bndlg.de/~max/apache

apache 2.2.3
http://wvbg.bndlg.de:81/~max/apache


Transfering the pictures to an apache running i386 debian and apache
1.3.34 everything works fine, too.

Any hints?


--
To UNSUBSCRIBE, email to debian-ia64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Brian Szymanski-5]

Have you watched the server via strace?

Seems like I get the first 1-2.5kB fine before bad things happen.

What happens if you make a plain text file of the exact same size?

Good luck,
Brian

Philipp Flesch wrote:

> Hi!
> We are running an HP RX2600 Itanium Server with debian eth (kernel
> 2.6.18) for some local education projects.
> Since we applied some updates (marked as non critical) via apt-get
> upgrade we have got problems with some jpgs.
>
> Loading the images via https everything works fine. Loading the images
> via http we got into a loop without generating any error in the logs.
> After resizing the picture with gimp the broken picture works fine.
>
> We found out, that some broken pictures have got EXIF-headers with
> camera information. Most of the pictures were uploaded months ago and
> have already been displayed without any problems before the "patchday".
>
> Please feel free to try out yourself:
>
> apache 1.3.34
> http://wvbg.bndlg.de/~max/apache vs. https://wvbg.bndlg.de/~max/apache
>
> apache 2.2.3
> http://wvbg.bndlg.de:81/~max/apache
>
>
> Transfering the pictures to an apache running i386 debian and apache
> 1.3.34 everything works fine, too.
>
> Any hints?
>
>

--
To UNSUBSCRIBE, email to debian-ia64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[dann frazier]

On Sun, Feb 01, 2009 at 11:48:42AM +0100, Philipp Flesch wrote:

> Hi!
> We are running an HP RX2600 Itanium Server with debian eth (kernel 2.6.18)
> for some local education projects.
> Since we applied some updates (marked as non critical) via apt-get upgrade
> we have got problems with some jpgs.
>
> Loading the images via https everything works fine. Loading the images via
> http we got into a loop without generating any error in the logs.
> After resizing the picture with gimp the broken picture works fine.
>
> We found out, that some broken pictures have got EXIF-headers with camera
> information. Most of the pictures were uploaded months ago and have already
> been displayed without any problems before the "patchday".
>
> Please feel free to try out yourself:
>
> apache 1.3.34
> http://wvbg.bndlg.de/~max/apache vs. https://wvbg.bndlg.de/~max/apache
>
> apache 2.2.3
> http://wvbg.bndlg.de:81/~max/apache
>
>
> Transfering the pictures to an apache running i386 debian and apache 1.3.34
> everything works fine, too.

I'd suggest figuring out what got upgraded (/var/log/dpkg.log is a
good reference) and reverting packages one by one back to the previous
versions to determine which change caused the difference.

--
dann frazier


--
To UNSUBSCRIBE, email to debian-ia64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Philipp Flesch]

Quoting dann frazier <dannf@...>:

>> Transfering the pictures to an apache running i386 debian and apache 1.3.34
>> everything works fine, too.
>
> I'd suggest figuring out what got upgraded (/var/log/dpkg.log is a
> good reference) and reverting packages one by one back to the previous
> versions to determine which change caused the difference.

I thought about that idea, too. But how to change to the previous  
version without knowing which one was installed?

Philipp


--
To UNSUBSCRIBE, email to debian-ia64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[dann frazier]

On Tue, Feb 03, 2009 at 10:57:05PM +0100, Philipp Flesch wrote:

> Quoting dann frazier <dannf@...>:
>
>>> Transfering the pictures to an apache running i386 debian and apache
>>> 1.3.34
>>> everything works fine, too.
>>
>> I'd suggest figuring out what got upgraded (/var/log/dpkg.log is a
>> good reference) and reverting packages one by one back to the previous
>> versions to determine which change caused the difference.
>
> I thought about that idea, too. But how to change to the previous version
> without knowing which one was installed?

/var/log/dpkg.log will tell you what packages got upgraded and list
both the previous and new versions.

--
dann frazier


--
To UNSUBSCRIBE, email to debian-ia64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Philipp Flesch]

Hi@all!
I recompiled Apache 2.2.11 and got the same problem.
Seems like the source of the fault is not apache ... but a lib used by
apache ...


dann frazier wrote:

> /var/log/dpkg.log will tell you what packages got upgraded and list
> both the previous and new versions.
>
>  
ok, i saved these log files ...
but I can not downgrade all dpg's upgraded since beginning of 2009 :-(
How to figure out which libs are used by apache?


--
To UNSUBSCRIBE, email to debian-ia64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Philipp Flesch]

Joost Witteveen schrieb:
> > How to figure out which libs are used by apache?
> Are these commands what you are looking for?
> $ ldd /usr/sbin/apache2
> $ dpkg -s apache2
>
exact! Thanks a lot!
That information reduces the accected libs ;-)

Last question:
Where can I find the older versions of several debian-packages?


--
To UNSUBSCRIBE, email to debian-ia64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...