Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 2844 invoked by uid 6000); 12 Nov 1999 00:35:56 -0000 Received: (qmail 2675 invoked from network); 12 Nov 1999 00:35:44 -0000 Received: from nebula.lyra.org (gstein@216.98.236.100) by taz.hyperreal.org with SMTP; 12 Nov 1999 00:35:44 -0000 Received: from localhost (gstein@localhost) by nebula.lyra.org (8.9.3/8.9.3) with ESMTP id QAA30616; Thu, 11 Nov 1999 16:34:55 -0800 Date: Thu, 11 Nov 1999 16:34:55 -0800 (PST) From: Greg Stein To: Vinod Mehra cc: apache-modules@covalent.net, new-httpd@apache.org Subject: Re: Resolving ebmedded image references in an HTML page In-Reply-To: <19991112003617728.AAA383@ashbury.weblogic.com@tehama> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Note: please use apache-modules for questions like this. Also, you had already sent this message without a subject line. Adding one and *resending* simply means that everybody gets spammed with multiple copies. Not to mention one copy for new-httpd and one for apache-modules. Now... to the question... On Thu, 11 Nov 1999, Vinod Mehra wrote: > and then passes it back to the client. The image references are not > getting resolved. > > eg. my request is like: > GET /acommand HTTP/1.1 > This returns an html page with an image refernce : for > /servletimages/trans.gif Is that the actual reference? With a leading "/" on it? If so, then that is how the web works! It means the reference is relative to the server, rather than the request-URI. Drop the leading "/" and the web browser should construct the final request properly. I'd recommend reading up on "relative URIs (URLs)" and "absolute URIs (URLs)" somewhere. No references right now, but any basic authoring book should discuss them. However, if you typoed and that leading "/" is *not* there, then I dunno. Your code looks fine. Cheers, -g -- Greg Stein, http://www.lyra.org/