Customer security is one of, if not the, top priority for us. We continually look for new ways to ensure our customers are safe, as well as improving our existing technology. With that in mind, we've recently upgraded Apache® on our Web servers to implement tighter security standards—protecting our customers from potential compromises.
However, with this upgrade comes some changes to how our environment handles
.htaccess. They're enabled by default from Apache 2.2 and onward, and enabling them results in an error.
.htaccessfile, your Website might display a "500 - Internal Server Error." To get more information, you can enable error logs to show you the cause of the error, which is similar to this:
.htaccessfile, we recommend adding a
-before the item you want to modify. Without using
-, our default (the most secure) Option replaces yours and, as a security precaution, Server-Side Includes become unavailable.
+Indexes" is the preferred way to enable directory browsing.
-Indexes" is the preferred way to disable directory browsing. This is also the default behavior.
[an error occurred while processing this directive] Error
Either 403 errors (such as no default/index file) or SSI handling can cause this error.
If it isn't a 403 error, how you fix this error depends on how the file generating the error references other files.
virtualelement starts at the root of the hosting account, e.g.
NOTE: The Server-Side Includes described here do not affect including files with dynamic scripting languages, such as PHP, Perl, or Python.