diff options
| author | Jiaqing Zhao <jiaqing.zhao@intel.com> | 2022-07-27 19:33:45 +0300 |
|---|---|---|
| committer | Ed Tanous <ed@tanous.net> | 2022-08-04 20:22:15 +0300 |
| commit | 81584abe2616373033281ab2ec75407fc50306d1 (patch) | |
| tree | 33391dd09de4f371c9e916014c7e4aad77f1e339 /http/utility.hpp | |
| parent | 827c4902835d3175a36d90808a51304f744203ce (diff) | |
| download | bmcweb-81584abe2616373033281ab2ec75407fc50306d1.tar.xz | |
log_services: PostCode: Do not populate nextLink when reaches end
According to Redfish spec 9.6.12 Next link (Members@odata.nextLink)
property, it shall only be present if the number of members in the
resource collection is greater than the number of members returned,
and if the payload does not represent the end of the requested resource
collection. This patch fixes the issue that the nextLink property will
always be present even if the request reaches end in PostCode LogEntry
collection.
Tested:
Verified Members@odata.nextLink in PostCode LogEntry collection is only
populated when ($top + $skip < Members@odata.count).
Redfish Service Validator passed.
Change-Id: I24feca331b279f62f00259e9ec5ca9a8d4c19557
Signed-off-by: Jiaqing Zhao <jiaqing.zhao@intel.com>
Diffstat (limited to 'http/utility.hpp')
0 files changed, 0 insertions, 0 deletions