Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 82949 invoked by uid 500); 7 Dec 2001 19:26:04 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 82937 invoked from network); 7 Dec 2001 19:26:03 -0000 Subject: C2: passing through straight HTML From: Rick To: cocoon-users@xml.apache.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0 (Preview Release) Date: 07 Dec 2001 13:26:06 -0600 Message-Id: <1007753167.2814.33.camel@punkadoodle.soils.wisc.edu> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N hullo all, we're doing a C2 app that's mostly XML-->XSLT stuff. but some of the docs offer links to old-fashioned, static HTML pages. we'd like to be able to just express a relative link in the XML source, to an HTML file that lives in the same directory as the XML. is there some quick-and-easy sitemap idiom for "just serve this as a static HTML file?" our alternatives seem to be (1) putting the static pages in the "regular" part of the web server, with absolute URLs in the XML source, and (2) adding rewrite rules to Apache to tell it "whenever you see this pattern that looks like it's going to cocoon but ends in HTML, just grab it from here instead." i'm not even sure that option 2 is viable, though. TIA, rw --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: