|
One comment. If you are using the IBM Original HTTP server I don't think it has the same capabilities as Apache, as far as parsing through the dynamic CGI output. At least I couldn't find it when I was having this same problem. . . hth, Aaron Bartell -----Original Message----- From: Justin Houchin [mailto:justin@reliatek.com] Sent: Monday, December 09, 2002 11:21 AM To: web400@midrange.com Subject: [WEB400] Web Menu problems This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] Hi Everyone, I am having a problem with a virtual file include. I am creating a set of web pages for our own use. These pages will have a set of menu options on the left side of the screen. These options will all be the same throughout the pages. So what I have done is created the menu options as a text file. I use a virtual include like <!--#include virtual="/customer_service/sidemenu.txt"-->, to copy the menu html source onto the page. This works great when the include is on a static web page. Here's the problem, I have a CGI program that writes a list of item categories. The HTML it uses has the include in it. When the program runs, it doesn't recognize the include. I think this is because the source is loaded into the memory and it is not treated as a standard "static" page. Is there a way around this? Justin Houchin Programmer and Web Developer www.reliatek.com justin@reliatek.com _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/web400 or email: WEB400-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.