Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <478B8046.4040206@joe-lewis.com>
Date: Mon, 14 Jan 2008 08:31:18 -0700
From: Joe Lewis <joe@joe-lewis.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20071031)
MIME-Version: 1.0
To: modules-dev@httpd.apache.org
References: <9dc7421e0801131158g361df65dpf026b5b05ff915bb@mail.gmail.com>
 <478B7277.4040909@joe-lewis.com>
 <9dc7421e0801140650q25f20749p450feaafe529e433@mail.gmail.com>
 <20080114150037.GE23798@suse.de>
In-Reply-To: <20080114150037.GE23798@suse.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Apache Module] Request External Redirection

Dr. Peter Poeml wrote:
> On Mon, Jan 14, 2008 at 03:50:25PM +0100, karim Bendadda wrote:
>   
>> Thanks for your answer! But I don't understand the second way to implement
>> it?? "it can respond with a Location: header and a status of 302."??
>>
>> On 1/14/08, Joe Lewis <joe@joe-lewis.com> wrote:
>>     
>>> karim Bendadda wrote:
>>>       
>>>>          I'm writing a module (MyModule_mod.c) wich has an *HTTP
>>>>         
>>> request* as
>>>       
>>>> input . I want to add an information to the request (an integer) and
>>>> redirect it to an *external *server ...Did you know any method for doing
>>>> this?
>>>>
>>>>
>>>>         
>>> There are two paths.  The server can PROXY to the external server (e.g.
>>> grab the result from the external server and then relay that to the
>>> client) or it can respond with a Location: header and a status of 302.
>>> Figure out which you wanted to do, and if you struggle to implement it,
>>> let us know.
>>>       
>
> In your handler, you would do something like this to implement the latter:
>
>     /* set a "Location:" header and 302 redirect. */
>
>     /* assemble the url by appending the filename to a baseurl */
>     uri = apr_pstrcat(r->pool, baseurl, filename, NULL);
>
>     apr_table_setn(r->headers_out, "Location", uri);
>
>     return HTTP_MOVED_TEMPORARILY;
>
> Peter
>   


Exactly!  What it does is forces the web client to go to the external 
server and request the resource/URI rather than the web server getting 
it for the web client.  It's a standard in the HTTP protocols that 302 
response codes work in a specific fashion.

Joe
-- 
Joseph Lewis <http://sharktooth.org/>
"Divide the fire, and you will sooner put it out." - Publius Syrus