I'll see if I can explain:
/application.cfc
/api.cfc
/web.config
If you call a URL structured in this manner "domain.com/method/function" then I have a url redirect in web.config that translates that to /api.cfc?method=init&function=functionname.
The api.cfc has an init handler that takes those URL params and calls the actual private function it has that matches those needs. This is heavily simplified, but you get the idea.
The application.cfc is a shell of a file, nothing is done in there at all. Just function outlines.
This ALL works fine except when the CFC itself returns a CF error. If you call the URL directly (as it was explained above) with a GET then you see the error. IF you use a HTML form to post to the page in a browser, you see the error. However if you POST data to that URL using CFHTTP then the connection times out based on the CFHTTP timeout param. The response is "connection timeout" in the CFHTTP vars and status code 200.
This is stumping me.