Got the url, but I don't know how this is supposed to enlighten us. The original calling code (SSI) is replaced by the content of the included files, leaving no trace of the what went on. Check your url references. I notice that in your posted code, there are a couple of different locations.
@ardav woops! didn't see what you were getting at but now I see that the code is just inserted without the reference. ok the original point was to see if there was some minor detail I was missing (looking at the same piece of code for hours leads you to think that you "know" it.)
Here is the code from the functioning site followed by the peculiarly coded include file called 'header':
Well, normally when I do includes my file extension is .txt or even .inc so there's no mistaking it for a full html page.
The link to the broken page is giving me a 'Directory Listing Denied This Virtual Directory does not allow contents to be listed.' This tells me the broken page is either 1. is not named index or default 2. is not there
But without having copies of the files for both the working version and the non-working version, there's not enough info to do much helping.
Advice: 1. make sure your main file is named index or default and has the proper extension. (Some servers will only serve up index.htm or index.html as default pages when the full address is not given.) 2. make sure the directory you're using for testing allows for includes. 3. make sure your links to the includes are correct AND the code inside them is valid. (The code inside the 'header.htm' has some issues - nested hrefs among other things.)
How can I make sure that the directory that I'm using allows includes? I maintain two main sites that share the same server so I would assume it does but I can't be sure.
"The link to the broken page is giving me a 'Directory Listing Denied This Virtual Directory does not allow contents to be listed.' This tells me the broken page is either 1. is not named index or default 2. is not there"
Does this mean that I NEED to have a directory with an index for include files to work? Is that a requisite?
The link http://cisr.jmu.edu/development/ lead me to an error page since the server is automatically looking for an index file since no file name was given in the link.
Server gets request for 'development/' Server looks at its personal setup file and goes 'Aha I'm suppose to look for index.htm, index.html, default.htm, or default.html. Oh, wait, I can't find any of those and I'm not supposed to show the file structure. Oops.'
Without looking at the broken file(s) and seeing what the server says is wrong, we can't do much.
If the main file is being rendered with warnings like 'error, cannot include file such and such' then includes are being allowed but the include file is either in the wrong place or misnamed (If the file being included was a Perl script then I'd also be looking at the error log for why the script failed.).
If there is no such warning but it's obvious the include file was NOT included then your directory does not allow them and you need to talk to whoever is in charge of the server and ask them to verify that includes are allowed in your development directory.
The other thing you can do give your main file a .shtml extension and see if that works. .shtml IS the normal extension for pages using includes. IF your development directory allows includes then that is your best bet.
Okay - it threw an error when you moved or tinkered with the include file - but when I look at the source I see the include comment - which means it's not processing the command. Change the file extension to .shtml or .shtm (those are the normal defaults for pages using SSI. If that doesn't work - talk with your IT people to get SSI activated for that directory.