By Date: <-- -->
By Thread: <-- -->

404 errors

Jason wrote:
> I think we need better HTTP code support somewhere in the core. If a module 
> believes an item being displayed is no longer available, then it should be 
> able to return a 404. Similarly, permissions errors, moved items, unexpected 
> errors etc. should all return the appropriate HTTP code. This does no mean 
> the user error should not be displayed, as that can be displayed as well.
>
Should be doable but its hard to come up with one global setting i 
think. It's value is part of the request-answer game we're playing, 
where the default answer is usually 200 (as in: all OK). The answer is 
part of the whole answer we put so much work in to construct, run the 
api, build the data, get the right template and sent it off.

The result code should be configurable for a number of situations. 
Redirect may be 301 (permanent) or 302 (temporary), exceptions may be 
404 (not found), no privilege for this (403?, 405? both?) or 500 
(boom!) or whatever we would like.

I think we only play with it in cache parts (304?) and perhaps uploads 
module. I suspect our default redirect is 302?
IIRC there's also the option to return multiple status codes?

Additionally, related to this, is better HTTP header control in general.

All in all, food for thought. I havent dived in recently.

marcel
_______________________________________________
Xaraya_devel mailing list
Xaraya_devel (at) xaraya.com
http://xaraya.com/mailman/listinfo/xaraya_devel