A typical proxy caches idempotent requests. The proxy gets the request, examines it for cache headers, and sends it to the server. Then the proxy examines the response and, if it is cacheable, caches it with the URL as the key (along with some headers in certain cases) and the response as the value. This scheme works well with GET requests, because for the same URL repeated invocation does not change the response. Intermediaries can make use of this idempotency to safely cache GET requests. But this is not the case with an idempotent POST request. The URL (and headers) cannot be used as the key because the response could be different – the same URL, but with a different body.
Anyway, what I am trying to achieve is really simple. We have deployed open-source Kibana 7.5.1 and I want to trigger POST/PUT endpoints for creating Space, Role, User etc.
This is part of some web-application project. When I try to create a Space for example, I get the error I mentioned above. It is CORS issue. Apparently Kibana is not allowing cross-origin requests.
The questions is: how can I enable it? I have access to kibana.yml and Kibana code.
The method requests data from the web server. It only returns the information about the web server and not the content itself. This s it faster than a GET request. Moreover, developers can include a custom header defined by their application to provide additional information or authentication credentials to the server. Here is the basic syntax for making a HEAD request:
I was trying to send an attachment using the POST Request. I do not find the suitable headers to include in the requests. What headers should be included in the requests?
