Same issue in 2.6.0 has been resolved to trigger a 'core.include.functions.redirectheader.start' event immediately before the 'core.include.functions.redirectheader' that the system module swallows if headers have not be sent. The same solution implemented for 2.5 series.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Same issue in 2.6.0 has been resolved to trigger a 'core.include.functions.redirectheader.start' event immediately before the 'core.include.functions.redirectheader' that the system module swallows if headers have not be sent. The same solution implemented for 2.5 series.