I'm not sure how all browsers interpret 'Location' HTTP headers, so maybe this will not work on all browsers, but...
I put a line 'exit;' at the end of function Request::redirect($url) in lib/Request.php which gives good speedup on e.g. plugins which call the redirect function.
Works for IE6.0sp1 on Windows 98. Other browsers might require additional HTTP headers and/or HTML to be emitted before the exit??
The previous behaviour was to continue generating a page which would not be displayed. The browser then loads the new page (i.e. target of the redirect), either when the invisible page is done (script finishes) or at some arbitrary time after seeing the 'Location' header.
(I discovered this when I had two WikiBlog plugins on the same page... comments were being submitted twice because the second plugin was executed even after the first one called the redirect.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure how all browsers interpret 'Location' HTTP headers, so maybe this will not work on all browsers, but...
I put a line 'exit;' at the end of function Request::redirect($url) in lib/Request.php which gives good speedup on e.g. plugins which call the redirect function.
Works for IE6.0sp1 on Windows 98. Other browsers might require additional HTTP headers and/or HTML to be emitted before the exit??
The previous behaviour was to continue generating a page which would not be displayed. The browser then loads the new page (i.e. target of the redirect), either when the invisible page is done (script finishes) or at some arbitrary time after seeing the 'Location' header.
(I discovered this when I had two WikiBlog plugins on the same page... comments were being submitted twice because the second plugin was executed even after the first one called the redirect.)