On Tue, 19 Jun 2007, A. Pagaltzis wrote:
This is getting a bit much – how about X-Public-URI-Base and letting the
frontend pass the full base URI to the backend. That would solve all the
mentioned problems in one fell swoop and might also address things that
haven’t occured to anyone yet, plus it’s much simpler than cobbling
together the URI from 5 different headers.
I did consider this when I started implementing this. However, this makes
it harder for a proxy to control how the backend handles URIs, by choosing
which things to tell it about. It also plain just doesn't work for things
like the path, since there's no way for the backend to know from a
forwarded URI that the proxy is serving things under a different base path
than the backend.
-dave
/*===================================================
VegGuide.Org www.BookIRead.com
Your guide to all that's veg. My book blog
===================================================*/
_______________________________________________
List: [email protected]
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
