Derek Gottfrid wrote:
I noticed an oddity and want to check and see if anybody else was
seeing the same issue.
If I call a eventlib http server w/ GET and Keep Alive and then
follow it up with a POST on the same connection, then I see a 400 Bad
Request message returned. If I just call the POST directly on the
first call it works fine since there is not Keep Alive in play. How
robust is the keep alive support? I will keep digging and can post
some sample code if it helps. Sorry for such newbie questions.
I think the keepalive support is reasonably good by now, at least in
trunk head. (What version are you using?)
I haven't tested that specific case, though, and I suspect no one else
has either. I deliberately avoid reusing connections for POST requests
when issuing requests, and I think most web browsers do the same. This
avoids an awkward situation where a non-idempotent requests can fail
because the server has timed out the connection, and it's not safe to
retry. RFC 2616 section 8.1.4 touches on this.
derek
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users
