You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GET
The GET method requests a representation of the specified resource. Requests using GET should only retrieve data and should not contain a request content.
POST
The POST method submits an entity to the specified resource, often causing a change in state or side effects on the server.
Unit version 1.34 should add support for POST requests for the same endpoints for restarts without removing support for GET requests.
We should also print a deprecation notice when folks are using GET request to issue a restart command to prepare them for its eventual removal in the following version tracked in #1446 .
The text was updated successfully, but these errors were encountered:
@hongzhidao had an excellent idea on Monday about this:
We could also support an endpoint where it’s not application specific, so instead of sending an empty (no body) POST to /control/applications/app_name/restart, we could send a POST to a new endpoint, like /control/applications with a POST body of
Currently the control API's message to restart a specific application is a GET request per the documentation: https://unit.nginx.org/configuration/#configuration-proc-mgmt
Semantically a GET request should not change state or have side effect on the server. It's more appropriate to use a POST request for this, see https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods
Unit version 1.34 should add support for POST requests for the same endpoints for restarts without removing support for GET requests.
We should also print a deprecation notice when folks are using GET request to issue a restart command to prepare them for its eventual removal in the following version tracked in #1446 .
The text was updated successfully, but these errors were encountered: