Comment 178 for bug 25830

(In reply to comment #147)
I'll keep this comment brief as this issue seems to be veering OT for this bug:

> For the second ("bad") link:
> $ telnet fisica 80
> Trying 194.117.43.10...
> HEAD /~jbatista/tstamp.c HTTP/0.9
>
> HTTP/1.1 200 OK
> Server: Apache/1.3.33 (Debian GNU/Linux) PHP/4.3.10-15 mod_ssl/2.8.22
OpenSSL/0.9.7d
> Content-Type: text/x-csrc

The curious thing here is that you've queried the same server for the same
file I queried in comment #146 and the server gave you a different content
type than it gave me. Even more curious, a couple of lines I clipped from
comment #146 to keep it brief, but still have in my xterm:

Trying 194.117.43.10...
...
Server: Apache/2.0.54 (Gentoo/Linux) PHP/4.3.11 mod_ssl/2.0.54 OpenSSL/0.9.7e

So, we've both connected to the same IP address, but got distinctly different
servers on different machines. I would guess fisica is doing some load sharing
among different machines behind the same outside IP, and they are configured
differently. Getting different content types for the same file on different
occasions could cause some puzzling symptoms. But probably beyond the scope of
this bug (except as another illustration of why it would be really useful to
be able to override the declared content type when needed).