If you're using POE::Component::Server::HTTP, you have to
set the 302 code in the response object, and then return
RC_OK from your handler. The component uses the return
values RC_OK, RC_DENY (not handled), RC_CONTINUE (show this
request to the next matching handler).

What the browser gets is the code you set in the $response
object.


--- Bob Faist <[EMAIL PROTECTED]> wrote:
> Not really a question but just sharing some info....
> 
> I used the suggestion by David to set the "Location" in
> the header and
> the 302 status code.  It turns out the problem was the
> HTTP status code
> I was returning from the content handler function was
> hard coded to be
> RC_OK.  If I set the status code to be 302 in the
> HTTP::Response object
> and then also returned "302" in the content handler
> function, the
> redirect in IE6 works just fine. 
> 
> Thanks,
> Bob
> 
> 
> -----Original Message-----
> 
>
**********************************************************************
> Confidentiality Notice
> The information contained in this e-mail is confidential
> and intended for
> use only by the person(s) or organization listed in the
> address. If you have
> received this communication in error, please contact the
> sender at O'Neil &
> Associates, Inc., immediately. Any copying,
> dissemination, or distribution
> of this communication, other than by the intended
> recipient, is strictly
> prohibited.
>
**********************************************************************
> 
> From: David Davis [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, April 14, 2005 1:26 PM
> To: Bob Faist
> Cc: [email protected]
> Subject: Re: HTTPD meta refresh
> 
> This isn't really a POE question, but I'll answer it.
> 
>
http://www.w3.org/TR/REC-html40/struct/global.html#edef-META
> -----
> Some user agents support the use of meta to refresh the
> current page
> after a specified number of seconds, with the option of
> replacing it by
> a different URI.
> Authors should not use this technique to forward users to
> different
> pages, as this makes the page inaccessible to some users.
> Instead,
> automatic page forwarding should be done using
> server-side redirects.
> ----- 
> 
> Use a Location: header and a 302 status to redirect the
> browser.
> --
> David Davis
> Perl Developer
> http://teknikill.net/
> 
> $7.95 per month hosting
> WITH ssh access
> http://hosting.teknikill.net/
> 
> 
> On 4/14/05, Bob Faist <[EMAIL PROTECTED]> wrote:
> > POE 0.3009 and POE::Component::Server::HTTP question
> > 
> > Windows XP
> > CGI::Application
> > 
> > The content handler provides a login page URL which is
> rendered 
> > correctly.  Once the form is submitted, the user is
> validated and the 
> > following HTML is returned to POE.
> > 
> > <HTML>
> >   <HEAD>
> >    <title>Authorizing...</title>
> >       <META http-equiv="refresh"
> >
>
content="0;URL=http://bfaist-ws:32080/cgi-bin/emsng_ietm_poe/IETM_Menu
> > .p
> > l">
> >   </HEAD>
> > </html>
> > 
> > This meta refresh works OK in Firefox but does not work
> OK in IE6.  
> > Any reasons why this would not work for IE?  If I run
> the CGI::App 
> > alone with Apache, it handles the meta refresh OK in
> Firefox and IE6.
> > 
> > There header attributes are being set in the response
> object.
> > 
> > [Thu Apr 14 12:30:53 2005] server.pl: Setting Date
> equals Thu, 14 Apr
> > 2005 16:30:53 GMT
> > [Thu Apr 14 12:30:53 2005] server.pl: Setting
> Set-Cookie equals 
> >
>
emsng_ietm_poe_session_key=acb3e60100360eb087b5f1219865c730;
> path=/ 
> > [Thu Apr 14 12:30:53 2005] server.pl: Setting
> Content-Type equals 
> > text/html; charset=ISO-8859-1
> > 
> >
>
**********************************************************************
> > Confidentiality Notice
> > The information contained in this e-mail is
> confidential and intended 
> > for use only by the person(s) or organization listed in
> the address. 
> > If you have received this communication in error,
> please contact the 
> > sender at O'Neil & Associates, Inc., immediately. Any
> copying, 
> > dissemination, or distribution of this communication,
> other than by 
> > the intended recipient, is strictly prohibited.
> >
>
**********************************************************************
> > 
> >
> 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Reply via email to