View Indexframe Shtml Portable 'link'

This guide explores the concept of "portable" navigation through these directory structures, turning a simple file list into a functional, on-the-fly file explorer.

5. Challenges of Viewing SHTML Locally

If you open indexframe.shtml directly in a browser (file:// protocol):

  • SSI directives appear as raw text or HTML comments
  • Included files are not merged
  • Frames may show broken paths
  • Variables like DATE_LOCAL are not replaced

Thus, a portable web server is required.

3. Why “Portable” Viewing?

Portable viewing means you can view indexframe.shtml without:

  • Installing a full web server permanently
  • Admin/root access
  • Internet connection (if assets are local)
  • Complex configuration

Use cases:

  • Archival research of old websites
  • Local testing of legacy projects
  • Offline documentation browsing
  • Distributing a website on USB drives

Step-by-Step: Viewing the Frames Correctly

Once you have a portable server running (Method 1), understanding the output of indexframe.shtml is crucial. view indexframe shtml portable

  1. Right-click inside the frame – Since it is a frameset, you cannot view the source of the entire page normally.
  2. View Frame Source: Right-click on the top frame -> "View Frame Source". This shows you the top_nav.shtml content.
  3. Inspect the Frameset: To see the master structure, right-click on a non-link area of the main window (or use Developer Tools) and view the parent source. You should see: 
    <frameset rows="100,*">
  <frame src="header.shtml">
  <frameset cols="200,*">
    <frame src="sidebar.shtml">
    <frame src="content.shtml" name="main">
  </frameset>
</frameset>

Method C: Using Python with Minimal SSI (Limited)

Save this script as ssi_server.py in your website folder:

import http.server
import socketserver
import re
import os

PORT = 8000


class SSIHandler(http.server.SimpleHTTPRequestHandler):
def do_GET(self):
if self.path.endswith('.shtml'):
file_path = self.path.lstrip('/')
try:
with open(file_path, 'r', encoding='utf-8') as f:
content = f.read()
# Process only #include virtual/file
def replace_include(match):
include_path = match.group(1)
if include_path.startswith('/'):
include_path = include_path[1:]
try:
with open(include_path, 'r', encoding='utf-8') as inc:
return inc.read()
except:
return f"<!-- SSI include failed: include_path -->"
content = re.sub(r'<!--#include (?:virtual|file)="([^"]+)" -->', replace_include, content)
self.send_response(200)
self.send_header('Content-type', 'text/html')
self.end_headers()
self.wfile.write(content.encode('utf-8'))
except Exception as e:
self.send_error(404, f"Error: e")
else:
super().do_GET()


with socketserver.TCPServer(("", PORT), SSIHandler) as httpd:
print(f"Serving at port PORT (limited SSI support)")
httpd.serve_forever()

Run:

python ssi_server.py

Then http://localhost:8000/indexframe.shtml

Note: This script handles only simple #include. No #echo, #if, or #exec.

Common Errors When Viewing indexframe.shtml Portably

If you try to simply double-click the file, you will likely see:

  • Plain text includes: <!--#include virtual="menu.shtml"--> displayed on the screen.
  • Broken frame paths: The browser tries to load file:///C:/menu.shtml instead of using the virtual path.
  • Missing CSS/JS: Relative paths break because the server context is missing.

The Fix: Always use a portable HTTP server. Even a basic Python HTTP server can be modified. If you have Python installed portably: This guide explores the concept of "portable" navigation

python -m http.server --cgi 8000

Note: The standard Python server does NOT parse SSI. You need the CGI script approach.

Part 3: The Portable Toolkit – 4 Methods to View the File

Here is the definitive guide to viewing indexframe.shtml without a permanent server installation.

Method 3: Dockerized Legacy Stack (The Modern Portable)

Best for: Reproducible archival.

Create a Dockerfile referencing Apache 2.2 (the last version that loved frames) with SSI enabled.

  • Command: docker run -p 8080:80 -v "$PWD":/usr/local/apache2/htdocs/ --name legacy-ssi httpd:2.2
  • Inside the container, enable mod_include.
  • View via localhost:8080.
  • Pros: Totally isolated, works on any OS with Docker.
  • Cons: Requires Docker installed (but Docker itself is portable via Docker Desktop Portable).