How to configure your web server for SwiftView

  1. Configure the mime types on your web server.  This is crucial.  See the section “HTTP Server Setup” documented in the plug-in readme notes .  Note that IIS 4 has a different means of setting mime types (don’t use regedit to change the registry)–  consult your IIS documentation.  Most servers require a total reboot for these mime types to take effect.  After you attempt to configure the mime types, view your SwiftView document with Netscape (not IE), click View, Page Info and read the information returned for File Mime Type.  If the correct mime type is not returned, check your webserver documentation and try again.
  2. Put npsview.lic in the root of your web server as per the Website Licensing Details.
  3. Check that your npsview.lic works by setting your system clock ahead one year and viewing a file on your website.  If you see the 30 second timeout, your license is not properly installed.
  4. Place an npsview.ics at the root of your web server.  You can put ICS commands in this file to configure SwiftView, e.g. to change the buttons or use markup.  But you must always have at least an empty file to prevent a hang in Firefox and other Netscape/Mozilla browsers.
  5. Provide your users with a means to install SwiftView.  See below.
  6. Try to avoid use of the suffix .ics for files on your webserver.  Use “.zhp” .  (.ics was “stolen” by Microsoft Calendar and can’t be used anymore.)
  7. If you use a “full page” control (i.e. not EMBED/OBJECT), your URL must in end one of the file suffixes SwiftView registers for (typically .zhp).  For more details on this and other flaws in Internet Explorer that can affect ActiveX controls, see Internet Explorer bugs.