* Nick Kew wrote: > Our subrequest API currently handles only local subrequests, > so for example mod_include doesn't support > <!--#include virtual="http://example.com/example.txt"-->. > I've worked around this in the past with some ugly hacks.
How ugly are they? I'd rather accept them than... > Looking at the code, it's actually very simple to build > in support for remote URLs into the subrequest mechanism > using mod_proxy. I've just test-driven a patch comprising > just six lines of code (attached), and it works. > > The patch still needs attention to escaping, but before > I deal with that, can I ask for votes on the concept? > Is there any reason not to add this feature? It opens a big can of worms. See the neverending story of faulty php scripts. -0 from here. I think this is a point where mod_include should stop. Besides that, shouldn't your patch trigger a gateway request instead of regular proxy? nd -- s s^saaaaaoaaaoaaaaooooaaoaaaomaaaa a alataa aaoat a a a maoaa a laoata a oia a o a m a o alaoooat aaool aaoaa matooololaaatoto aaa o a o ms;s;\s;s;g;y;s;:;s;y#mailto: # \51/\134\137| http://www.perlig.de #;print;# > [EMAIL PROTECTED]
