an error occurred while processing this directive

Hi There,

I am getting the followig error, when I try to preview the generated html

"an error occurred while processing this directive"

I have SSI setup configured. This works fine on my DEV ENV (http), but not on UAT (https).

Any clue?

Regards,

Find more posts tagged with

Comments

Shazam

Hi Jay,

This error typically occurs when either the syntax for your SSI is not correct, of if the server settings have not been made to understand and allow SSI files.

Also, I have never used SSI files on a secure server (HTTPS), so there may be some issue there, not sure.

What is the server's operating system? On Apache, all works fairly easily as long as the server has been set up correctly. I set up shtml as the extension for all of my SSI files, and just pull them into the html

Windows is a different beast, but it can work.....there are certain things you have to do by the book though. Such as, the extension for the file that is PULLING the SSI file MUST end in SHTML. I don't like this, but have had to deal with it in the past. If anyone has found a way to work around this, let me know! ;-)

I would also suggest checking your code to make sure it is calling correctly; are you calling a file using virtual, or vice versa, is the syntax correct? Then, I would check the server settings to make sure that SSI files are not only allowed, but that the proper extension has also been added.

I hope this helps, at least a little. :-)

Suzanne

Hi There,

I am getting the followig error, when I try to preview the generated html

"an error occurred while processing this directive"

I have SSI setup configured. This works fine on my DEV ENV (http), but not on UAT (https).

Any clue?

Regards,

Adam Stoller

...
Windows is a different beast, but it can work.....there are certain things you have to do by the book though. Such as, the extension for the file that is PULLING the SSI file MUST end in SHTML. I don't like this, but have had to deal with it in the past. If anyone has found a way to work around this, let me know! ;-)
...

FYI - that isn't true - it's just that .shtml is the default extension that IIS provides for processing SSI directives. You can configure it to work with .htm and .html files too (we're doing so at my current customer's site)

With respect to the thread however ... I just tested here and when I change a URL from http://... to https://... it seems to stop working - but that's on their actual web servers that I don't believe were configured for https. In TeamSite's IIS, I seem to be able to use http or https without any problems. So I imagine it is a server setting of some sort.

Shazam

Fish,

Let me make sure I understand....you are able to use html or htm file extension for the files that are PULLING the SSI into the page, correct? I am not talking about the actual SSI file, but the file that pulls the SSI.

If this is correct, can you please point me to a source for this, and let me know what version of Windows the server is running you are working with?

Everything I found stated that only SHTML could be used on a Windows server. I thought that was insane, but had to make every page in the website an shtml file, regardless whether the page was pulling the SSI or was the SSI file. I would LOVE to use html for the normal pages and use shtml for all of the actual SSI files.

Thanks! ;-)

Yeah, I am thinking that his https server hasn't been configured for SSI yet.

Suzanne

FYI - that isn't true - it's just that .shtml is the default extension that IIS provides for processing SSI directives. You can configure it to work with .htm and .html files too (we're doing so at my current customer's site)

With respect to the thread however ... I just tested here and when I change a URL from http://... to https://... it seems to stop working - but that's on their actual web servers that I don't believe were configured for https. In TeamSite's IIS, I seem to be able to use http or https without any problems. So I imagine it is a server setting of some sort.

Adam Stoller

Fish,

Let me make sure I understand....you are able to use html or htm file extension for the files that are PULLING the SSI into the page, correct? I am not talking about the actual SSI file, but the file that pulls the SSI.

If this is correct, can you please point me to a source for this, and let me know what version of Windows the server is running you are working with?

Everything I found stated that only SHTML could be used on a Windows server. I thought that was insane, but had to make every page in the website an shtml file, regardless whether the page was pulling the SSI or was the SSI file. I would LOVE to use html for the normal pages and use shtml for all of the actual SSI files.

Thanks! ;-)

Yeah, I am thinking that his https server hasn't been configured for SSI yet.

Suzanne

In IIS on W2K3 - in the MMC right-click on the web-site and select Properties, then click on the Home Directory tab, and click on the Configuration... button.
Find the entry for .shtm - edit it - copy the Executable path and Cancel the edit.
Edit or Add an entry for .htm (and/or .html) - paste in the Executable path and set the extension (if necessary) to .htm (or .html) - we limited the verbs to POST,GET and have "Script engine" and "Verify that file exists" both checked. Click OK to save the setting, click OK to save the mappings.
Click on the ISAPI Filters tab and add the entry for iwrewrite that references IWHOME\lib\iwproxy_isapi.dll - click OK to save that, click OK to save everything, and then stop / start the web site.