Loading src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +13 −16 Original line number Diff line number Diff line Loading @@ -2014,7 +2014,7 @@ components: a single consecutive byte range from the content of the VNF package file has been read successfully according to the request. The response body shall contain the requested part of the VNF package file. The "Content-Range" HTTP header shall be provided according to IETF RFC 7233. The "Content-Range" HTTP header shall be provided according to IETF RFC 9110. The "Content-Type" HTTP header shall be set as defined above for the "200 OK" response. headers: Content-Range: Loading Loading @@ -2176,7 +2176,7 @@ components: Shall be returned when the whole content of the archive containing the artifact files has been read successfully. The payload body shall be a ZIP archive containing the requested The message content shall be a ZIP archive containing the requested set of artifacts selected according to the provisions specified above in this clause, and, if the flag "include_signatures" was provided in the related request, the applicable signature files and, if available, Loading Loading @@ -2219,7 +2219,7 @@ components: successfully according to the request. The response body shall contain the requested part of the archive. The "Content-Type" HTTP header shall be set to "application/zip". The "Content-Range" HTTP header shall be provided according to IETF RFC 7233. The "Content-Range" HTTP header shall be provided according to IETF RFC 9110. headers: Content-Range: required : true Loading Loading @@ -2261,7 +2261,7 @@ components: been read successfully. If the "include_signatures" request URI parameter was not provided in the related request, the payload body shall contain a copy of the artifact the related request, the message content shall contain a copy of the artifact file from the VNF package, as defined by ETSI GS NFV-SOL 004 and the "Content-Type" HTTP header shall be set according to the content type of the artifact file. If the artifact is encrypted, the header shall be set to the value "application/cms" Loading @@ -2269,7 +2269,7 @@ components: to the value "application/octet-stream". If the "include_signatures" request URI parameter was provided in the related request, the "Content-Type" HTTP header shall be set to "application/zip and the payload body the "Content-Type" HTTP header shall be set to "application/zip and the messgae content shall contain a ZIP archive which includes: • a copy of the artifact file from the VNF package, as defined by ETSI GS NFV SOL 004; • the related security information (individual signature file and optional related Loading Loading @@ -2305,17 +2305,14 @@ components: description: | 206 PARTIAL CONTENT If the NFVO supports range requests and the "include_signatures" request URI parameter was not present in the related request, this response shall be returned when a single consecutive byte range from the content of the artifact file, if the NFVO supports range requests has been read successfully according to the request. The response body shall contain the requested part of the VNF package file. The "Content-Range" HTTP header shall be provided according to IETF RFC 7233. The "Content-Type" HTTP header shall be set as defined above for the "200 OK" response. If the NFVO supports range requests and the "include_signatures" request URI parameter was not present in the related request, this response shall be returned when a single consecutive byte range from the content of the artifact file has been read successfully according to the request. The response body shall contain the requested part of the artifact file from the VNF package, as defined by ETSI GS NFV-SOL 004. The "Content-Type" HTTP header shall be set according to the content type of the artifact file. If the content type cannot be determined, the header shall be set to the value "application/octet-stream". The "Content-Range" HTTP header shall be provided according to IETF RFC 9110. headers: Content-Range: required : true Loading src/SOL003/VNFPackageManagement/definitions/SOL003VNFPackageManagement_def.yaml +2 −2 File changed.Contains only whitespace changes. Show changes Loading
src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +13 −16 Original line number Diff line number Diff line Loading @@ -2014,7 +2014,7 @@ components: a single consecutive byte range from the content of the VNF package file has been read successfully according to the request. The response body shall contain the requested part of the VNF package file. The "Content-Range" HTTP header shall be provided according to IETF RFC 7233. The "Content-Range" HTTP header shall be provided according to IETF RFC 9110. The "Content-Type" HTTP header shall be set as defined above for the "200 OK" response. headers: Content-Range: Loading Loading @@ -2176,7 +2176,7 @@ components: Shall be returned when the whole content of the archive containing the artifact files has been read successfully. The payload body shall be a ZIP archive containing the requested The message content shall be a ZIP archive containing the requested set of artifacts selected according to the provisions specified above in this clause, and, if the flag "include_signatures" was provided in the related request, the applicable signature files and, if available, Loading Loading @@ -2219,7 +2219,7 @@ components: successfully according to the request. The response body shall contain the requested part of the archive. The "Content-Type" HTTP header shall be set to "application/zip". The "Content-Range" HTTP header shall be provided according to IETF RFC 7233. The "Content-Range" HTTP header shall be provided according to IETF RFC 9110. headers: Content-Range: required : true Loading Loading @@ -2261,7 +2261,7 @@ components: been read successfully. If the "include_signatures" request URI parameter was not provided in the related request, the payload body shall contain a copy of the artifact the related request, the message content shall contain a copy of the artifact file from the VNF package, as defined by ETSI GS NFV-SOL 004 and the "Content-Type" HTTP header shall be set according to the content type of the artifact file. If the artifact is encrypted, the header shall be set to the value "application/cms" Loading @@ -2269,7 +2269,7 @@ components: to the value "application/octet-stream". If the "include_signatures" request URI parameter was provided in the related request, the "Content-Type" HTTP header shall be set to "application/zip and the payload body the "Content-Type" HTTP header shall be set to "application/zip and the messgae content shall contain a ZIP archive which includes: • a copy of the artifact file from the VNF package, as defined by ETSI GS NFV SOL 004; • the related security information (individual signature file and optional related Loading Loading @@ -2305,17 +2305,14 @@ components: description: | 206 PARTIAL CONTENT If the NFVO supports range requests and the "include_signatures" request URI parameter was not present in the related request, this response shall be returned when a single consecutive byte range from the content of the artifact file, if the NFVO supports range requests has been read successfully according to the request. The response body shall contain the requested part of the VNF package file. The "Content-Range" HTTP header shall be provided according to IETF RFC 7233. The "Content-Type" HTTP header shall be set as defined above for the "200 OK" response. If the NFVO supports range requests and the "include_signatures" request URI parameter was not present in the related request, this response shall be returned when a single consecutive byte range from the content of the artifact file has been read successfully according to the request. The response body shall contain the requested part of the artifact file from the VNF package, as defined by ETSI GS NFV-SOL 004. The "Content-Type" HTTP header shall be set according to the content type of the artifact file. If the content type cannot be determined, the header shall be set to the value "application/octet-stream". The "Content-Range" HTTP header shall be provided according to IETF RFC 9110. headers: Content-Range: required : true Loading
src/SOL003/VNFPackageManagement/definitions/SOL003VNFPackageManagement_def.yaml +2 −2 File changed.Contains only whitespace changes. Show changes