Roberto A. Foglietta wrote:
http://www.roberto.foglietta.name/pub/dillo/
It able to refresh AND redirect, but only if -r option is specified in command line. May be you can modify it to refresh ALWAYS and use -r option ONLY for redirect when time is more than the specified offset
-r <seconds>
The more I think about how I'd go about hacking this functionality in, the more questions it brings up... As well as a time boundary, I think it would probably be best to include another option to specify which refreshes to honour. At the moment it's a simple choice between 1 (default): no refresh 2 (with -r): all refreshes permitted Rather than changing the first to be "refresh only, no redirect", could I suggest some kind of choice between the following three? 1: no refresh 2: refreshes allowed, redirects not 3: refreshes + redirects permitted And then we get into the murky area of limiting the times for these. Could/should it be a different value for refreshes and for redirects? What to do if the page requests a shorter timeout than allowed: ignore it altogether, or handle after the minimum timeout has elapsed? Is that too many command-line options? Would an entry (or several) in dillorc be more suitable? Glyn