ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> modperl
modperl
Re: Fixing a mod_perl module
by Geoffrey Young other posts by this author
Dec 8 2006 10:27AM messages near this date
Fixing a mod_perl module | MODPERL and Reverse Proxy
Grant wrote:
>  Hello, I'm on the Interchange mailing list (icdevgroup.org) and we've
>  found a problem with our Interchange::Link mod_perl module for
>  apache2.  I don't know perl myself, and I was wondering if anyone here
>  might be able to help fix it.
>  
>  The problem is that the Interchange tag:
>  
>  [bounce href="http://www.domain.com" status="301 moved"]
>  
>  uses the default 302 code when Interchange::Link is used.  It uses the
>  specified 301 without Interchange::Link.  The problem has been
>  isolated to this portion of code from Interchange::Link :
>  
>  if($set_status =~ /^30[21]/) {
>  #warn "Doing redirect\n";
>   $r->content_type($set_content);
>   close (SOCK)                                or die "close: $!\n";
>   return Apache2::Const::REDIRECT;
>  }

Apache2::Const::REDIRECT is 302 and is equivalent to
Apache2::Const::HTTP_MOVED_TEMPORARILY.  if you want 301 you will want
to use Apache2::Const::HTTP_MOVED_PERMANENTLY.

HTH

--Geoff
Thread:
Grant
Geoffrey Young

Privacy Policy | Email Opt-out | Feedback | Syndication
© 2004 ActiveState, a division of Sophos All rights reserved