On Fri, Apr 23, 2010 at 01:19:28AM +0000, corvid wrote:
Jorge wrote:
So perhaps the nav redirection stuff should use bw->redirect_level.
This looks like a good idea. If you want to make a patch go ahead, I'll look at the expect url issue with zero-delay refresh now.
I see that, in Cache_process_queue(), redirect_level is zeroed if CA_Redirect isn't set. I wonder whether, since this is http-equiv, it should reach into cache in a way that's similar to Content-Type and let us rip out the nav redirection code.
This may be a sleeping dragon. It could look cleaner if handled in cache, but there's a need to sync the redirecting-URL not to end in the history stack, while at the same time letting the resource finish loading and to assert repush works OK (part of this is achieved by using a timeout in nav). Maybe it can be done easily, I don't know yet. Although I remember very well that "charset" given by HTML's META was a royal PITA to handle! (chicken/egg problem). ATM we're handling zero-delay redirection for root URLs only. I see little use for generalizing it to child resources. I see clear gain in the case of HTTP redirection. My point is: it could take a significative effort that would be better spent on something more urgent/strategic for the project. -- Cheers Jorge.-