If you are running on Microsoft Internet Information Services (IIS), SHTML handling is different.
You must explicitly tell Apache to allow server-side includes within your website directory. Add the Includes option to your configuration block:
<FilesMatch "\.shtml$"> SSILegacyExprParser On </FilesMatch>
sudo nginx -t sudo systemctl reload nginx
Nginx has built-in SSI support, but it is disabled by default. When disabled, Nginx treats .shtml files as standard text, displaying raw code or prompting a file download. 1. Modify the Server Block
If your site is serving or linking to a view.shtml file and you're seeing errors (500s, missing content, raw SSI not processed, or broken includes), this guide walks through common causes and fixes so your server correctly handles Server Side Includes (SSI) and the view.shtml page renders as intended.
What (Apache, Nginx, IIS) or hosting provider are you using?
Note: If your hosting provider blocks global option overrides, using Options +Includes might trigger a "500 Internal Server Error." If this happens, remove the line and contact your host to enable SSI. Fix 2: Configure Nginx for SSI Processing
How to Fix SHTML Files Not Displaying or Rendering Properly If you visit a website or work on a server and see raw code instead of a completed webpage, the server is failing to parse Server Side Includes (SSI) inside an SHTML file. SHTML files are standard HTML documents that contain server-side directives to inject dynamic content, such as headers, footers, or timestamps, before the page reaches the browser.
If you are seeing raw code, or if your includes are not appearing, it usually means the server is not configured to treat .shtml files as "parsed" or the includes are malformed. Common Symptoms:
: Make a file named test.shtml with the following content:
If you are running on Microsoft Internet Information Services (IIS), SHTML handling is different.
You must explicitly tell Apache to allow server-side includes within your website directory. Add the Includes option to your configuration block:
<FilesMatch "\.shtml$"> SSILegacyExprParser On </FilesMatch> view shtml fix
sudo nginx -t sudo systemctl reload nginx
Nginx has built-in SSI support, but it is disabled by default. When disabled, Nginx treats .shtml files as standard text, displaying raw code or prompting a file download. 1. Modify the Server Block If you are running on Microsoft Internet Information
If your site is serving or linking to a view.shtml file and you're seeing errors (500s, missing content, raw SSI not processed, or broken includes), this guide walks through common causes and fixes so your server correctly handles Server Side Includes (SSI) and the view.shtml page renders as intended.
What (Apache, Nginx, IIS) or hosting provider are you using? When disabled, Nginx treats
Note: If your hosting provider blocks global option overrides, using Options +Includes might trigger a "500 Internal Server Error." If this happens, remove the line and contact your host to enable SSI. Fix 2: Configure Nginx for SSI Processing
How to Fix SHTML Files Not Displaying or Rendering Properly If you visit a website or work on a server and see raw code instead of a completed webpage, the server is failing to parse Server Side Includes (SSI) inside an SHTML file. SHTML files are standard HTML documents that contain server-side directives to inject dynamic content, such as headers, footers, or timestamps, before the page reaches the browser.
If you are seeing raw code, or if your includes are not appearing, it usually means the server is not configured to treat .shtml files as "parsed" or the includes are malformed. Common Symptoms:
: Make a file named test.shtml with the following content:
DownLoad:
