<br><br>
<div><span class="gmail_quote">On 05/06/06, <b class="gmail_sendername">Zed Shaw</b> <<a href="mailto:zedshaw@zedshaw.com">zedshaw@zedshaw.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">but you actually need to mount rails at / and<br>then use Rail's routing and settings to tell it it's at a different base
<br>URI. Otherwise weirdness ensues.</blockquote>
<div> </div>
<div>That looks like your good reason for hard coding '/' to me. I presume from what you are saying that Mongrel simply matches the URI to determine a handler and passes the entire URI to the Handler intact. Any rewriting is pushed forward to the front-end dispatcher or backwards to the application itself.
<br> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">If setting it to some other URI solves something for you then let me<br>know what. Might be another solution you're not aware of.
</blockquote>
<div> </div>
<div>It was really to test hanging an application off a different base URI without having to mess around altering Rails routing or setting up rewriting rules on a webserver.</div>
<div> </div>
<div>Plus I have this idea in the back of my mind that the webserver should really be replaced with something else that is lighter and faster - particularly as with an app layer that talks HTTP the webserver is reduced to little more than a glorified load balancer. However at the moment we seem to need it for its URL rewriting and re-rooting capability.
</div>
<div> </div>
<div>NeilW</div></div>