Heh, just ran into a POST corruption issue on 10.5 with a managed account.

Turns out there's a transparent HTTP proxy for these managed accounts. And
the transparent proxy doesn't handle Expect: 100-continue correctly.
After getting back the 100 status from the server, the proxy resends the
HTTP headers rather than the body. Whoops...

You can disable curl sending the expect header explicitly by setting the
header Expect header to blank or by telling curl to use HTTP/1.0.

On the command line, you would use the -0 (zero) option to use HTTP/1.0. TO
clear the expect header, you can pass -H 'Expect:'

-Costa

On Tue, Sep 15, 2009 at 12:00 PM, Michael Wood <esiotrot_at_gmail.com> wrote:

> 2009/9/15 Daniel Stenberg <daniel_at_haxx.se>:
> [...]
> > Sorry, but I don't really see what libcurl does wrong or what I can do to
> > track this down from my end. I don't have a mac and I'm convinced this
> isn't
> > a libcurl flaw. This basic sending of a POST is fairly well tested and
> used
> > and if it was that broken we would've gotten far more reports about it.
> >
> > I think you should direct your focus on the parental control software and
> > whoever creates that.
>
> It's part of the OS. It's just an option (or set of options) you can
> enable when creating an account.
>
> --
> Michael Wood <esiotrot_at_gmail.com>
>
Received on 2009-09-16