Operations
Overall there are no structural changes to logging elements. But there are new error messages added withing access logs to aid in debugging this condition.
The following error messages can be found in the access logs when certain conditions occur:
| Status | Code | Access Log error message | Notes |
|---|---|---|---|
| 400 | InvalidRequest | "The included forbid overwrite header contains an invalid value." | |
| 409 | ObjectAlreadyExists | "An existing object cannot be overwritten because the forbid overwrite header was specified in the request." | This is the main failure condition for this feature. If a user includes a forbid overwrite header in the request, and this write request results in an overwrite of an existing object on a nonversioned bucket, a failure is generated |
| 400 | InvalidRequest | "The request must contain no more than one forbid overwrite header." | For example, user includes x-ibm-forbid-overwrite and x-oss-forbid-overwrite headers in the same request. |