(12-21-2014, 05:47 PM)ivantcholakov Wrote: "I think the 404_override is preferable for this reason. Unless I'm missing something..."
It might work, I don't know, but you probably will need to prevent 404 http return code on your ordinary pages instead of 200. And also the case of real 404 error would need to be detected. Sounds complicated to me.
The http code is 200 when it hits your 404_override controller. I expect I'll have some pretty particular logic which can reliably distinguish a valid request from a bogus one. It may be fairly complicated, but the our search is complicated. My original reason for wanting this fallback controller is to parse the request and implement some previously existing search logic without the restrictions of a mod_rewrite file or routes.php or the default CI controller/method routing. PHP will give me a lot more flexibility.
