Er, okay. The thing is, this is *trivial* with Apache and
fcgi--just add 'RewriteBase /blog/' to your usual rewrite config and it Just
Works. Routes work correctly in both directions.
So
can you not do the same with the proxy? Mongrel is a replacement for
FCGI, not the Apache/FCGI pair.
If
Rails knew which prefix it lived on and could generate all its refer and
redirect URLs relative to that prefix rather than just root, then you wouldn't
need a rewriter proxy - Mongrel could just pass the URL in and out
unadulterated. Should Rails know where it lives in the URL tree though? Is
that the job of the application or the web server?
Perhaps the solution
to the 'loads of http proxy front ends' is to consider that none of them are
fit for *our* purposes - much as FCGI wasn't fit for the application server
purpose. Anybody got to the stage where that itch is worth
scratching?
NeilW
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users
