That particular error message in FireFox usually means one of two
things... either there's an issue with cookies, or something's off in
your server configuration and/or .htaccess files (I got this once when
I accidentally deleted an .htaccess file).
On Jun 29, 4:51 am, RLR [EMAIL PROTECTED]
A bit off topic, but I was taught to always structure your code so
that execution terminates by falling out the bottom of you routines
(i.e. no early exit points). For one, it makes more logical sense in
execution flow and is typically easier to maintain. So if you have any
clean-up code at the
Except that what you write in a controller action is only one part of
what Cake does with a request, and calling exit() is the quickest way
to skip all of that. Setting autoRender to false will stop the view
from being rendered, but I'm not sure what else would need to be done
to end the whole
I am having a tough time tracking down what is wrong!
The problem seems to be two fold:
I am using an auth component from the bakery which I load via the
beforeFilter in app_controller and redirect to /auth/ and present a
login view if no vaild session user can be found.
When I access the app
I had this problem a few times, when redirecting to the same URL
with a different variable
/movies/count_votes/
when it finished, i redirected to the same action, to update other rows
/movies/count_votes/500
/movies/count_votes/1000
and so on.
The problem is, if i didn't put an exit(); after
A 404 is generated by your server - not the client.
Is the 404 generated by Cake, or by your webserver? If by cake, set
the DEBUG to 1 and see what the real error is (ie missing model/view/
controller file). If by your webserver, then the request isn't even
getting to cake - so look at your