On Fri, 16 Jan 2009, Toby White wrote:

> The URI is simply a reference to a resource, and the server is promising to
> do various things according to what HTTP verb I send; if I do a GET I'll get
> a representation of what's there, if I do a PUT I'll overwrite that
> representation. Whether the URI ends in a forward slash doesn't affect that.
>
> I appreciate that the behaviour of -T makes perfect sense when writing to a
> filesystem, or something pretending to be one, but in this case it's not, I
> want to be able to do a PUT straight to the URI I specify.

I agree that the current -T behavior doesn't make a lot of sense for HTTP but
the code that does the appending of the file name to the end of the URL if it
ends with a slash doesn't care about protocol. I'd say we have a reason to
reconsider that.

But as long as it works like this, I figure you either 1) fix curl 2) find a
work-around or 3) try another tool. I would of course favor exactly that
order, but...

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html