Communicate with server using PUT

Dar Scott dsc at swcp.com
Thu Jun 27 19:56:48 EDT 2013


This is coming back to me and I think I ended up testing the PUT on a different server.  Perhaps some Apache setting was getting in the way and the ISP was not able to track it down.  I still wonder if my test had some flaw staring me in the face.  In any case, I was able to do the test.

Dar

On Jun 27, 2013, at 8:46 AM, Trevor DeVore wrote:

> On Thu, Jun 27, 2013 at 10:00 AM, Dar Scott <dsc at swcp.com> wrote:
> 
>> I have had trouble with PUT.
>> 
>> I worked with the ISP to make sure it was enabled.  I set up the right
>> access file permissions.  I made sure to put the name and password in the
>> URL.  And failure.
>> 
>> So, either there was some overriding setting at the ISP that blocked
>> things or either me or liburl is broken.
>> 
> 
> Dar,
> 
> I've used libURL for years to send PUT calls to my servers so I don't think
> it is libURL. It is the call used whenever you are updating a resource on
> the server. I recall that a few years ago I had to mimic PUT by doing a
> POST with a parameter specifying that the server should process as a PUT.
> This was a ruby on rails issue IIRC, however.
> 
> -- 
> Trevor DeVore
> Blue Mango Learning Systems
> www.clarify-it.com    -    www.screensteps.com
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode





More information about the use-livecode mailing list