Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.2.1
Request #5734 Redirect via '<meta http-equiv="Refresh"'
Submitted: 2005-10-20 17:09 UTC
From: sprice Assigned: avb
Status: Closed Package: HTTP_Client
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 50 - 26 = ?

 
 [2005-10-20 17:09 UTC] seth at pricepages dot org
Description: ------------ Would it be possible to add redirect support when the redirect is via: <META http-equiv="refresh" content="5;<URL>"> and the content-type header is "text/html". I have already implemented part of this and would be willing to submit a patch.

Comments

 [2005-10-30 19:19 UTC] seth at pricepages dot org
Well, patch is here: http://pricepages.org/pear/Client.metaTag.diff.zip
 [2005-11-07 20:09 UTC] avb
The regex requires a bit of polishing, it will not handle f.e. the following: <meta content="1, URL=..." http-equiv="Refresh"> or <meta http-equiv='Refresh' content='1, URL=...'> Also the 60-second limit seems a bit arbitrary.
 [2005-11-08 22:38 UTC] seth at pricepages dot org
The file at http://pricepages.org/pear/Client.metaTag.diff.zip has been updated with a new patch that should be smarter about such things. The 60 second redirect, though, is arbitrary. I figure that 60 seconds is enough time for someone to actually get some meaningful information off of a page, so therefore the redirect after that time may be counter-intuitive. Feel free to change it if you want.
 [2006-06-03 08:57 UTC] avb (Alexey Borzov)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.