Michael Petnuch wrote:
> Hello,
>
> I just upgraded to the new version of Dispatch. Everything went
> smooth, I didn't have to change anything. However, I have been getting
> a strange error. I checked out the code and it seems that at the end of
> the handler method $r->status is being set (its value is 200). This
> value is associated with everything is Okay. However because the status
> is being set it triggers the http_error method (I think)
The status doesn't trigger a call to http_error, an exception in your
application, or in the URL parsing does.
> and I see this
> appended to the html output:
If it's appended, then it probably means that your application finished it's run
mode and postrun. I'd suspect that something is wrong in your teardown.
[snip]
> Shouldn't Dispatch check to see if the status is 200.
I'm not sure where you're talking about. How can it check if the status is 200
if it's running as the handler? It's the component that sets the status.
> I was confused
> because it sends either $r->status || OK();. If I am seeing this does
> it mean that their is something wrong with my setup (maybe an Apache
> config this).
I suspect something in your teardown phase. Is there anything in your apache
error log? Dispatch should be ignoring any errors thrown by your application
unless it's the "No such run mode" error, which becomes a NOT_FOUND error.
--
Michael Peters
Developer
Plus Three, LP
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
|
