After more research on this, I have found that this setting is ON by default. The documentation is wrong. Many have confirmed that on the net. So, it is normal that this behavior is happening. I do not want to change it to OFF as this is a valid security mechanism in place that is good to have. However, as I have the log in my error, it means the code goes into my framework. So, I will trap this error and redirect to the main page with a message when this is happening. However, I have the feeling that this will act exactly like the other situation I had when the response object is not loading on a specific situation. If that is the case for this situation as well, it means I will not be able to get a handle on the response object, thus not able to redirect to a page.