Template security preferences do not allow remote access...

[burritonator]

If anyone tries to access a file on our Apache Web Servers with an ".htm" extension, the following error message appears in their browser:

"Error: template security preferences do not allow remote access to files with that extension".

I have tried searching the Net for help with this issue, but all I find are links to files on other web servers that are having the same problem. I haven't been able to find a discussion of the problem anywhere.

Can anyone tell me what would cause this error, and how to correct it?

Thanks

 

[sleipnir214]

This sounds more like a browser issue than a server issue.

Have you tried another brand of browser?


Want the best answers? Ask the best questions!

TANSTAAFL!!

 

[burritonator]

It doesn't appear to be a browser issue, as I have tried IE and Firefox, and I receive the same error in both. I think that our Sys Admin tried some additional browsers as well. The same problem also occurs on both PCs and Macs in our organization.

Also note that I have verified that I can open ".htm" files that reside on some other servers. However, if you Google the phrase "Template Security Preferences", you'll find links to many other sites that are having the same problem (although sometimes with different file extensions).

 

[sleipnir214]

Yeah, I see what you mean. A number of other servers are exhibiting the same problem. But at least one of those sites is running WebStar, not Apache.

I also searched both the Apache 1.3.33 and 2.0.53 source tarballs for the string "template security preference" and came up empty.


Are you running any kind of content manager on this server? Do you have any non-standard modules plugged in?


Want the best answers? Ask the best questions!

TANSTAAFL!!

 

[burritonator]

It turns out I was on the wrong track in looking for a solution to this problem. Our servers also use WebDNA, and it turns out that the problem was with WebDNA instead of Apache. WebDNA contains security settings where the allowed file extensions must be explicitly entered, and htm wasn't in the list. We just hadn't found those settings right away because we didn't initially realize the problem was with WebDNA.