>-----Original Message----- >From: Christopher Schultz [mailto:ch...@christopherschultz.net] >Subject: Re: Baked-in context paths > >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA256 > >Leo, > >> >I think it's worth pointing-out that the original discussion (at least from >BZ) was >about browser-facing links, not just named files as you have above. >
I am also talking about browser facing links. > >To be clear, Milo wasn't objecting to "static links" -- that is, stupidly >putting <a >href="/contextname/path"> into a page where "contextpath" if changed would >require you to edit every page on your site. > >- -chris I'm not sure I meant it that way. Another example: http://gis.rdsa.maricopa.gov If you have Firefox, view the image info for the globe icon in the upper left. It should be relative to the "root" context. http://gis.rdsa/maricopa.gov/oppositioncase This same image is referenced via the context path for "oppositioncase" and physically deployed in this context's path, since it would be of no use if I wanted to move this and only this web app to another domain. The source code for side_nav_left.xhtml in the oppositioncase context: <div class="divcontent"> <h1 class="color_header"> <a href="/index.xhtml" class="home" title="PlanNet Home">Home</a> </h1> <div id="leftnav"> <div class="leftnavlogo"> <img alt="PlanNet Logo" title="PlanNet Logo" src="resources/images/PlanNet.gif" /><br /> </div> <hr /> <table width="100%"> <tr> <td colspan="2"> </td> </tr> <tr> <td align="center" colspan="2"> <div class="leftnavspacers"> <a class="fade_upper" href="/plannet/PlanNetGuide.pdf" title="PlanNet Help Topics" target="_blank">PlanNet Help Topics</a> </div> </td> </tr> </table> </div> </div> Leo
