Inets 4.0 and HTTP/1.1 "100 Continue" responses
Mon Dec 6 15:53:14 CET 2004
Heinrich Venter wrote:
> >This can be handy if the client has a big body that it wants to send
> and it does not
> >want to send it if the server will reject the request. In this case the
> next response
> >will not be sent by the server until it receives the body from the
> Ahhh, I see. Thanks for clearing this up for me :)
> >> The assumption that every response will have its own socket event
> >> seems to be wrong. If the 100-continue (and its supposedly empty
> >> Body) is
> >I have made no such assumption!
> Its only the 100-continue without the expect header that breaks the
> pattern realy, because there is more than one response to one request.
> Is there a better way to handle this than re-parsing the Body?
Well after some consideration I will have to partyl change my mind ;)
and agree with you that in the case will need to reparse the body.
Ericsson AB - OTP team
More information about the erlang-questions