put

I am trying to add a repo to a team on github, thus: curl -i -u username:password -X PUT -d "" https://api.github.com/teams/:team/repos/:user/:repo (specifics left out) Pretty much as indicated in the not so verbose documentation. This gives a 500 Internal server error . If I leave out the -d"" it gives a 411 "Content-Length required" , if I specify (using -H ) "Content-Length: 0" : again the 500 error... Any clues? [edit] Answer: the API was giving spurious responses and the docs are not very good there: " :team " is a numerical id assigned by the system (not the name you gave it .. arg!) -

I have constructed a single-node Hadoop environment on CentOS using the Cloudera CDH repository. When I want to copy a local file to HDFS, I used the command: sudo -u hdfs hadoop fs -put /root/MyHadoop/file1.txt / But,the result depressed me: put: '/root/MyHadoop/file1.txt': No such file or directory I'm sure this file does exist. Please help me,Thanks! Alfonso Nishikawa As user hdfs , do you have access rights to /root/ (in your local hdd)?. Usually you don't. You must copy file1.txt to a place where hdfs user has read rights. Try: cp /root/MyHadoop/file1.txt /tmp chown hdfs:hdfs /tmp/file1

I'm trying to make a request via SSL. The certificate is already installed on the machine and it works via browser. I am using this request: System.Text.ASCIIEncoding encoding = new System.Text.ASCIIEncoding(); byte[] data = encoding.GetBytes(request.Content.OuterXml.ToString()); string password = "XXXX"; X509Certificate2 cert = new X509Certificate2("c:\\zzzz.p12", password); string key = cert.GetPublicKeyString(); string certData = Encoding.ASCII.GetString(cert.Export(X509ContentType.Cert)); Uri uri = new Uri(request.Url); HttpWebRequest myRequest = (HttpWebRequest)WebRequest.Create(uri);

I keep a key-value storage in the server for the client. If the user sends key "k1", then I upsert it to the database. Is this considered POST or PUT ? Also I have another operation that removes all existing keys and adds the new key. Is this POST or PUT because it clears records and adds a new one. If the user send key "k1" then I upsert it to the database. Is this considered POST or PUT. According to the HTTP specification : The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an already existing resource, the enclosed entity

I'm seeing many frameworks recently that have decided to "fake" PUT and DELETE requests. Like Ruby on Rails. They seem to be waiting for browsers to catch up. Are they waiting in vain? Is this even slated to be implemented anywhere? Nicholas Shanks Browsers do support PUT and DELETE , but it's HTML that doesn't. For example, a browser will initiate a PUT request via Javascript (AJAX), but not via HTML <form> submission. This is because HTML 4.01 and the final W3C HTML 5.0 spec both say that the only HTTP methods that their form elements should allow are GET and POST. There was much discussion

I need to create an HTTP PUT request using ruby. The request has a JSON body I was able to generate the JSON body using: require 'rubygems' require 'json' jsonbody = JSON.generate["message"=>"test","user"=>"user1"] I need to send this PUT request to the url: require 'open-uri' url = URI.parse('http://www.data.com?access_token=123') Can someone please tell me how I can do this in Ruby? Using restclient ( gem install rest-client ) like this: require 'rubygems' require 'rest_client' require 'json' jdata = JSON.generate(["test"]) RestClient.put 'http://localhost:4567/users/123', jdata, {:content

I'm in the middle of implementing a RESTful API, and I am unsure about the 'community accepted' behavior for the presence of data that can not change. For example, in my API there is a 'file' resource that when created contains a number of fields that can not be modified after creation, such as the file's binary data, and some metadata associated with it. Additionally, the 'file' can have a written description, and tags associated. My question concerns doing an update to one of these 'file' resources. A GET of a specific 'file' will return all the metadata, description & tags associated with

So, I can successfully make a GET call to my service using CORS. However, something must be going wrong at the preflight level for the POST, PUT, and DELETE operations. However, from what I can tell, the header responses my server is returning in response to the OPTIONS query are correct and match those described in Here is my javascript code, using $.ajax in JQuery 1.6.4. $.ajax({ url: 'http://myhome:8080/TaskApproval/resources/tasks/2', context: this, data: '<?xml version="1.0" encoding="UTF-8"?> <task> <description>Get carrots from the grocery store</description><originator>Chris<

To be more precise: According to rest style, it's generally assummed that POST, GET, PUT, and DELETE http methods should be used for CREATE, READ, UPDATE and DELETE (CRUD) operations. In fact, if we stick to the http methods definition the thing might not be so clear In this article it's explained that: In a nutshell: use PUT if and only if you know both the URL where the resource will live, and the entirety of the contents of the resource. Otherwise, use POST. Mainly because PUT is a much more restrictive verb. It takes a complete resource and stores it at the given URL. If there was a