Level
To see this image in actual size, you need to save it or open it in separate tab. Use context
menu (right click).
To share this image you need also save it first. It's experimental feature, it's only halfway
done, forgive the inconvenience.
: Administrators often use an indexframe.shtml file to wrap these plain lists in a custom layout, adding branding, search bars, or contact links to an otherwise bare directory.
: Iframes can be independently scrollable. view indexframe shtml link
<!DOCTYPE html> <html lang="en"> <head> <title>My SSI Site</title> <link rel="stylesheet" href="/css/main.css"> </head> <body> <!-- Inject the Navigation --> <!--#include virtual="/includes/nav.shtml" --> <!-- Main Content Area (The IndexFrame body) --> <div class="content"> <!--#include virtual="/includes/hero.shtml" --> <p>Welcome to the live site.</p> <!--#include virtual="/includes/footer.shtml" --> </div> : Administrators often use an indexframe
The links called load('gallery/'), which worked only if gallery/ returned an HTML page. Apache, however, was configured to treat .shtml files specially and to map directory requests through indexframe.shtml via a rewrite rule—so every request got the same wrapper. That explained the reload loop. Apache, however, was configured to treat
However, your query is a bit too brief to give a precise answer. Could you clarify what you need? For example:
While SSI is "old school," it is still incredibly useful for static sites that need a splash of dynamic assembly. If you are maintaining a legacy intranet or a high-traffic blog that doesn't need a database, mastering the <!--#include virtual--> directive will save you hours of copy-pasting.
