Sorry, the 'joe' should have been jpe (thanks, autocorrect). Anyway, I removed jp and used the line you suggested but I still get the image as a download rather than viewing it in the browser window...
Damn, if I try viewing a .jpg from this site in a browser window, it works fine...
-Scott
[doublepost=1463164454][/doublepost]I'm asking on an Apache forum why some of my images get served with the correct headers but not others... e.g.:
[x@saabnet class]# curl -I
http://www.saabnet.com/images/spamcop.jpg
HTTP/1.1 200 OK
Date: Fri, 13 May 2016 18:16:59 GMT
Server: Apache/2.2.25 (Unix)
Last-Modified: Fri, 01 Dec 2006 01:38:49 GMT
ETag: "54401f1-9453-423810fc27c40"
Accept-Ranges: bytes
Content-Length: 37971
Connection: close
Content-Type: image/jpeg
X-Pad: avoid browser bug
vs
[x@saabnet class]# curl -I
http://www.saabnet.com/tsn/class/131015ccaarsm.jpg
HTTP/1.1 200 OK
Date: Fri, 13 May 2016 18:19:00 GMT
Server: Apache/2.2.25 (Unix)
X-Powered-By: PHP/4.4.9
Connection: close
Content-Type: image/jpg
-Scott[/QUOTE]
I am assuming that you are stopping/starting Apache between your changes.
The interesting thing about your sample is that the first appears to be a direct load by Apache while the second one appears to be related to PHP processing. Maybe PHP is contributing to the problem. If PHP is involved, you may want to check if PHP is setting the content type.
DS