On Thu, 19 Jul 2012, Dima Tisnek wrote:

> Hi, I'm getting a whole bunch of these in my private web server logs:
>
> [Wed Jul 18 11:22:26 2012] [error] [client 193.64.20.129] Invalid
> method in request ------------------------------c5a4fa5b03a9

> It looks like server expects a new request, POST /xxx HTTP xxx, but
> instead gets a multipart post separator.

Right, looks like something very broken.

> All (most) the clients are pycurl/libcurl/openssl with http keepalives and
> ssl session caching and they send multipart POST requests, only very small
> percentage of these requests triggers this.
>
> All the broken requests come over 3G connection, I suspect slow/unreliable
> network connection triggers the bug.

But what's the nature of your server and the clients here? You say pycurl, so
I figure this is a custom client somehow?

> Did anyone see anything like this before?
>
> Where do I start digging?

It would help if you could figure out the exact request your server receives
when it complains.

> Should the socket be closed if client sent POST headers and failed to submit
> post data per spec?

Yes.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html