Re: hopefully simple project
Chris Lightfoot <[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <ZgZsSAkQemR6.UOIaE2eMrmLeOIbw7/[email protected]> |
On Thu, Dec 28, 2006 at 07:01:10PM +0200, Yonah Russ wrote: > On 12/28/06, Chris Lightfoot <[email protected]> wrote: [...] > >wrapping the script is possible but a little nontrivial > >(your wrapper script would have to implement the fastcgi > >IPC protocol and state machine). I would do this by making > >the `wrapper' actually fetch pages from the original > >script over HTTP, and return them to the client; then > >restrict access to the real app so that it will only > >serve pages to the wrapper, and point external clients at > >the wrapper script. > > I was afraid of something like that. I'm not sure what you suggest would > work in this case because the cgi tracks information such as referals, > source ip, etc. Proxying the requests would probably block some of the > information- no? well... you can reconstruct all of the headers from the client's request from the HTTP_... variables in the environment (though if these include Authorization: you will have to force apache to pass those through). You can add an X-Forwarded-For: header identifying the originating IP; there are third-party modules from apache which fix things up so that this will be represented to scripts as the real client IP if it was added by a trusted server. So it should be possible to achieve what you want. -- `Unlike the FAA, Bin Laden has a coherent Weltanschaung that a person of average intelligence might understand. The real madman is the guy who banned nail scissors. By the way, if they confiscate your clippers, a bottle of duty free Scotch makes a spiffing cosh.' (Harry Hutton flies the friendly skies) ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/