Well, it’s a new command, so I would suggest changing it. I find that in most cases of a modern web app, you’re doing a temporary redirect, not a permanent. 301 was really messing me up because the browser would cache it, and then I’d have to blow away my cache to make things work again.
So, I would humbly suggest we leave that command just like it is. The [headers redirect] can keep the same semantics for backward compatibility. > On Dec 15, 2014, at 3:13 PM, Massimo Manghi <[email protected]> wrote: > > The 301 (http://en.wikipedia.org/wiki/HTTP_301) is the permanent > redirection so, in order to keep the 'permanent' semantics consistent, > the default must be 1 > > -- Massimo > > On 12/15/2014 06:51 PM, Damon Courtney wrote: > >> proc ::rivet::redirect {url {permanent 0}} { >> no_body ; ## don’t output anything on a redirect >> headers set Location $url >> headers numeric [expr {$permanent ? "301" : "302"}] >> abort_page ; ## stop any further processing >> } >> >> Damon >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
