Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 84940 invoked by uid 500); 15 Jan 2002 07:59:03 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 84929 invoked from network); 15 Jan 2002 07:59:02 -0000 Received: from noella.mindsec.com (209.172.192.12) by daedalus.apache.org with SMTP; 15 Jan 2002 07:59:02 -0000 Received: from localhost (IDENT:100@localhost [127.0.0.1]) by noella.mindsec.com (8.11.6/3.0.3) with ESMTP id g0F7xED27831 for ; Mon, 14 Jan 2002 23:59:14 -0800 (PST) Date: Mon, 14 Jan 2002 23:59:14 -0800 (PST) From: Erik Parker To: users@httpd.apache.org Subject: RE: mod_rewrite and apache In-Reply-To: Message-ID: X-Use-Encryption: Encrypt your messages to me with PGP or GPG! X-GPG-Key: http://www.mindsec.com/staff/eparker/gpg.txt MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N JS> Can't be done with any standard Apache module. You want apache to scan JS> through each document as it is served and do a search/replace. Mod_rewrite JS> acts only on the URL that is actually requested, not on the document JS> contents. After you said that, it became very clear :) I guess for now, I'm going to use SSI and do an if $SSL == on, write out img src="https:/foo else img src="http://foo It's not ideal, but it will work until this client can get their code split apart into seperate sections. It's not too bad though, these systems lack memory, and speed, not processor.. so I think short term, they shoul dbe ok with the SSI's. Thanks, -Erik --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org