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
This may be embracing REST semantics too much, but a PUT is technically supposed to replace the content of the resource at the URL with the content in the request.
For CFs, this would mean truncating the CF and then doing the same sort of thing as PATCH on the CF (described in the other issue I just posted).
The net effect of both issues would then be:
A PUT with no data on a CF ensures it exists and is empty.
A PUT with data on a CF replaces the content with the content of the request.
A PATCH with no data on a CF ensures it exists (but will not truncate it).
A PATCH with data on a CF works as described in my other issue.
The text was updated successfully, but these errors were encountered:
This may be embracing REST semantics too much, but a PUT is technically supposed to replace the content of the resource at the URL with the content in the request.
For CFs, this would mean truncating the CF and then doing the same sort of thing as PATCH on the CF (described in the other issue I just posted).
The net effect of both issues would then be:
A PUT with no data on a CF ensures it exists and is empty.
A PUT with data on a CF replaces the content with the content of the request.
A PATCH with no data on a CF ensures it exists (but will not truncate it).
A PATCH with data on a CF works as described in my other issue.
The text was updated successfully, but these errors were encountered: