Hi!

I don't have any idea what to attribute this to, but I know that there was a hardware replacement on our server this weekend. Still, I can't fathom how that would explain anything, but here goes.

Without changing stylesheets, a background image in a div will not display, and my Web Developer toolbar utility tells me this image is broken:

http://www.coreknowledge.org/CK/index.htm

   1. http://www.coreknowledge.org/CK/images/rshade2.png

The image is there on the server, with the correct permissions (644), but oddly, one cannot browse to it, unlike all my other background images.

Compare with a similar background image:
   http://www.coreknowledge.org/CK/images/BRtcurveshade2.png

The images are working fine in Dreamweaver, and when tested locally on my computer, with many different web browsers.

What I've tried to do so far, with no success:

1. Replaced Rshade2.gif with rshade2.png
2. Added "display:block; position:relative" to the div where that image goes; no dice.
3. Reformatted the CSS from correct background-image:, background-display; background-position; to single line "background: url(../images/rshade2.png) repeat-y right;" like the other background images; no change.
4. Recreated the graphic, in case there was something wrong with the file
5. Renamed the graphic

What's bizarre is the "broken link" and image not being available. When one tries to go to the image directly, one gets this odd server message:

A profound puzzle to me... perhaps I need to bring this to the attention of tech support???

thanks for any advice

... edit: I'm positive this is a server problem. The exact same image, renamed as test.png displays, the image rshade2.png or rshadetwo.png or Rshade2.gif does not display.

The image files are returning a 406 header response which is rather odd. Try changing the file name to an entirely different base name and see if the problem continues. In order to find the cause you might want to add the following to your .htaccess file to see if it changes the issue.

<IfModule mod_security.c>
SecFilterEngine Off
</IfModule>

The name of the file starts with rsh, and some protective software somewhere may be "censoring" that to prevent use of the "rsh" (remote shell) command. I've seen discussion board posts have that happen, but not in HTML or PHP code. For discussions and blogs, the .htaccess lines

# cancel mod security
SecFilterEngine Off
SecFilterScanPOST Off

works -- perhaps it will work for you too. Anyway, the file itself is fine; it's just the name that PHP and the server are possibly objecting to. If it doesn't work, try a name that doesn't start with "rsh". I don't know if it will object to that string in the middle of a name.

Just to chime in here, since we got a ticket and doesn't appear anyone gave a yes/no answer yet.

File names that start with rsh are forbidden on linux servers due to the potential running of shell commands.

It should not affect file names such as "marsh.jpg" but will block such as "rshade2.png".

This is done to insure the security and stability of the shared servers.

Now off for a pizza...