...Really the only bit I need some conceptual help with is continuing processing the response once the user has been redirected.� I could potentially use a cinclude, and use the same request as issued by the client, but that just seems a bit hacky.� Does anyone have any other ideas?...
Maybe you could pass the non-cached request URL to the stdin of a different process (or via an HTTP request) which would make the same request with a "don't redirect" option?
I'm thinking of a simple wget-like thing which accepts URLs asynchronously, and later makes requests to them and throws away the result.
It might be easier to test and monitor than an "internal" solution, sounds easy to implement and you'd be sure that all the components of the actual user request would be generated.
But it depends on your definition of "hacky" ;-)
-Bertrand
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
