[cse491] [cse491[ 404 Not Found
C. Titus Brown
ctb at msu.edu
Tue Nov 3 08:42:51 PST 2009
On Tue, Nov 03, 2009 at 11:39:48AM -0500, Garrett Radford wrote:
> Do we need to implement this for our non-blocking server as well or
> are we done with that?
If you are implementing it so that it matters whether you use
NonblockingServer or Server, you are doing it wrong.
That having been said, I will only be looking at webserve. (Actually, I will
primarily be looking at apps.py ;)
--titus
>
> On Tue, Nov 3, 2009 at 11:32 AM, C. Titus Brown <ctb at msu.edu> wrote:
> > On Tue, Nov 03, 2009 at 11:30:39AM -0500, Garrett Radford wrote:
> >> When we are returning 404 Errors (i.e. status = '404 Not Found'), for
> >> either a bad path, files missing or an IOError, what should we return
> >> back to our webserve? All I do right now is change the status to '404
> >> Not Found', change the headers to a content-type of text/html, start
> >> the response and return data = ''. I was looking for the standard 404
> >> Error Page, but I just get a blank page (obviously because I'm
> >> returning nothing). Is this 404 page something you're looking for or
> >> can I just leave it as it is?
> >
> > It's up to you; I won't be looking at anything but the status line.
> >
> > --
> > C. Titus Brown, ctb at msu.edu
> >
--
C. Titus Brown, ctb at msu.edu
More information about the cse491-fall-2009
mailing list