Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 75780 invoked by uid 500); 4 Jul 2002 19:44:39 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 75760 invoked from network); 4 Jul 2002 19:44:39 -0000 Message-ID: <3D24A5E5.10206@yahoo.de> Date: Thu, 04 Jul 2002 21:45:41 +0200 From: "J.Pietschmann" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [RT] Cocoon Blocks References: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Piroumian Konstantin wrote: > If your sitemap is somewhere in WEB-INF then having sitemap.xml would be > obvious, but if you have sitemap in the same directory where your content > files are located then one could view your sitemap by simply typing > 'sitemap.xml' in request path. To prevent this you would have to setup a > special pipeline in your sitemap or use resource constraints in web.xml. Does using "sitemap.xmap" prevent illegal access? J.Pietschmann --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org