You need to add CA of your certificate to your transport like: package main import ( “crypto/tls” “io/ioutil” “log” “net/http” “crypto/x509” ) func main() { caCert, err := ioutil.ReadFile(“rootCA.crt”) if err != nil { log.Fatal(err) } caCertPool := x509.NewCertPool() caCertPool.AppendCertsFromPEM(caCert) client := &http.Client{ Transport: &http.Transport{ TLSClientConfig: &tls.Config{ RootCAs: caCertPool, }, }, } _, err := … Read more
I don’t see how REST adds a constraint that two resources could not have the same value. The resourceType/ID is just an example of the easiest use case rather than the best way to go from a RESTful point of view. If you read paragraph 5.2.1.1 of Roy Fielding’s dissertation carefully, you will notice that … Read more
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 … Read more
POST to this URL https://<JIRA_HOST>/rest/api/2/issue/ This data: { “fields”: { “project”: { “key”: “<PROJECT_KEY>” }, “summary”: “REST EXAMPLE”, “description”: “Creating an issue via REST API”, “issuetype”: { “name”: “Bug” } } } In received answer will be ID and key of your ISSUE: {“id”:”83336″,”key”:”PROJECT_KEY-4″,”self”:”https://<JIRA_HOST>/rest/api/2/issue/83336″} Don’t forget about authorization. I used HTTP-Basic one.
I strongly oppose 404 in favour of 204 or 200 with empty data. Or at least one should use a response entity with the 404. The request was received and properly processed – it did trigger application code on the server, the client might not have made any mistake, and thus the whole class of … Read more
The difference can be found in the specifications, in this case RFC 7231: 5.3.2. Accept The “Accept” header field can be used by user agents to specify response media types that are acceptable. 3.1.1.5. Content-Type The “Content-Type” header field indicates the media type of the associated representation The Accept header always indicates what kind of … Read more
Few things to be clarified here are: GET /?service=turn&username=mbzrxpgjys which returns a JSON, is just a suggested uri for retrieving time-limited TURN credentials from the server, you do not have to follow that, your uri can be just /?giveMeCredentials. In fact, I use my socket connection to retrieve this data, not direct http call with … Read more
An API Gateway is a proxy provided for the client. The Gateway gives the client a consistent interface regardless of any changes within the internal system. It allows the internal system to change without affecting the client. The API Gateway can also provide consistent cross-cutting concerns such as security logging, reporting and API analytics. An … Read more
Since POST is an “append” operation, it might be more Englishy to POST to /products, as you’d be appending a new product to the existing list of products. As long as you’ve standardized on something within your API, I think that’s good enough. Since REST APIs should be hypertext-driven, the URI is relatively inconsequential anyway. … Read more
You should use POST – using GET for these actions can lead to issues with browser prefetching and search engine spidering. See (1, 2)