[api-ref]Allow SLO PUTs to forgo per-segment integrity checks

[OpenStack Infra]

https://review.openstack.org/184479
commit bb716573ab5c8455348ec013feb894421e0e1f1c
Author: Tim Burke <email address hidden>
Date: Wed May 20 00:39:41 2015 -0700

    Allow SLO PUTs to forgo per-segment integrity checks

    While manifests still require 'etag' and 'size_bytes' fields for each
    segment (to catch user errors like 'etaf' or 'size_btyes'), an explicit
    null for either will skip that particular integrity check and instead
    use whatever value is retrieved when HEADing the segment. So, if a user
    uploads a manifest like:

        [{"path": "/con/obj_seg_1", "etag": null, "size_bytes": 1048576},
         {"path": "/con/obj_seg_2", "etag": "etag2", "size_bytes": null},
         {"path": "/con/obj_seg_3", "etag": null, "size_bytes": null}]

    then the etag will only be verified for the /con/obj_seg_2 segment,
    and the segment size will only be verified for the /con/obj_seg_1
    segment. However, the manifest that's ultimately stored (and can be
    retrieved with a ?multipart-manifest=get query-string) will still look
    like:

        [{"name": "/con/obj_seg_1", "hash": "etag1", "bytes": 1048576, ...},
         {"name": "/con/obj_seg_2", "hash": "etag2", "bytes": 1048576, ...},
         {"name": "/con/obj_seg_3", "hash": "etag3", "bytes": 1234, ...}]

    This allows the middleware to continue performing integrity checks on
    object GET.

    Change-Id: I2c4e585221387dd02a8679a50398d6b614407b12
    DocImpact

[Lana (loquacity)]

This is an API doc change only.

[Atsushi SAKAI (sakaia)]

Let me clearify this issue

This issues for checking criteria changes for PUT methods.
But, PUT checking criteria is not documented on api-ref.
So I guess it is not affect to api-ref.
Is my understanding correct?

[Tim Burke (1-tim-z)]

Should've looked at this a while ago, but yeah, SLO segment integrity doesn't seem to be documented in api-ref; I think this is safe to close.