dank at EECS.Berkeley.EDU
Tue Oct 30 02:36:53 PDT 2007
Go with a 400 Bad Request
something like what Lisa said:
HTTP/1.0 400 Bad Request: ERROR -- Invalid characters following the protocol string
----- Original Message -----
From: Lisa Fowler <fowler at EECS.Berkeley.EDU>
Date: Monday, October 29, 2007 8:29 pm
Subject: Re: [ee122] spurious
> Ah, sorry. Daniel needs to answer this one. I see your question is
> if there should be a "HTTP/1.0 400 Bad Request: ERROR -- Invalid
> characters following the protocol string" returned from the server in
> the case of spurious tokens after the method token.
> Daniel's say is the final say on that. Daniel?
> On 10/29/07, Lisa Fowler <fowler at eecs.berkeley.edu> wrote:
> > Treat all (appropriate) errors from Milestone A, such as this
> one, as
> > 400 Bad Request errors.
> > -Lisa
> > On 10/29/07, benjlau at berkeley.edu <benjlau at berkeley.edu> wrote:
> > > What happened to the spurious text before CRLF message from
> Phase 1?
> > > Someone earlier, I think it was Ben Wang, asked about this but
> there was
> > > no response and I can't find any info relating to its
> disappearance on the
> > > mailing list. Has it just been integrated into the Invalid
> HTTP Version
> > > message? Or do we just simply completely ignore spurious text
> now? Sorry
> > > if this was mentioned but I cannot find it and since the
> earlier question
> > > was not answered I wonder if it was just forgotten.
> > >
> > > _______________________________________________
> > > ee122 mailing list
> > > ee122 at mailman.ICSI.Berkeley.EDU
> > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/ee122
> > >
More information about the ee122