Neo SPCC launched tailor-made updates to each NeoFS gateways in early July, masking the REST API interface and the S3-compatible protocol gateway. REST Gateway v0.18.0 was launched on July third and S3 Gateway v0.45.0 was launched on July 2nd, each releases concentrating on efficiency enhancements, API floor cleanup, and shared dependency upgrades.
This replace follows an analogous sample to the earlier gateway pair launched in April, which launched session token v2 help in REST v0.17.0 and S3 v0.43.0. Each new releases depend on NeoFS SDK RC20 and NeoGo v0.120.0 and are aligned with the just lately lined NeoFS Node v0.54.0, finishing an improve cycle for the complete stack.
REST Gateway v0.18.0
The REST Gateway launch introduces help for non-ASCII object attributes by a brand new characteristic. X-Attributes-Base64 header system. As a result of normal HTTP headers are restricted to printable ASCII, the gateway accepts attribute metadata as a Base64-encoded JSON map, enabling object attributes in Cyrillic, Chinese language, emoji, and different non-ASCII encodings. heritage X-Attributes Headers can nonetheless be used as a fallback if all attribute values are ASCII secure.
Two efficiency enhancements have been made to GET operations. The gateway skips SHA256 checksum verification on downloaded objects and eliminates computation of the total payload hash on each request. Inside buffer dealing with has additionally been refactored to cut back reminiscence allocation overhead when studying objects. readCloseWriterTo Interface that enables zero-copy knowledge switch to HTTP response writers. These adjustments notably have an effect on downloads of huge objects.
new X-Object-Sort Response headers are hooked up to the article GET and HEAD The response permits API customers to tell apart between: REGULAR, TOMBSTONE, LOCKand LINK Object sort. This launch additionally provides help for origin tokens. /v2/auth/session/full Endpoint. Preserves the delegation chain when a session token is derived from a mother or father token.
By way of cleansing, RANGEHASH Prerequisite operational help enabled by the NeoFS SDK RC20 improve has been eliminated. The authentication endpoint now accepts each hex and Base64 encoding. key and signature Area that beforehand solely accepted hexadecimal numbers.
No configuration adjustments are required for customers upgrading from v0.17.x, however the utility X-Attributes Headers for objects with non-ASCII metadata ought to be migrated to . X-Attributes-Base64.
S3 Gateway v0.45.0
The S3 Gateway launch contains new options and efficiency enhancements, in addition to some breaking adjustments. Customers upgrading from older variations ought to overview the migration necessities earlier than continuing.
new namespace A configuration possibility permits namespace-only gateway mode, which scopes all requests to a particular namespace. This addresses consumer preferences for bucket subdomains and namespace scoping.
Dealing with of HEAD requests has been optimized by integrating two inside decision paths. SEARCH operation plus one HEAD to single SEARCH plus one HEAD It runs on a per-request foundation, lowering community round-trips to NeoFS storage nodes. Checksum verification can also be disabled Get Handlers for efficiency and EACL guidelines have been simplified as follows: GETRANGEHASH to cut back desk measurement and get rid of duplicate entries. reminiscence points CompleteMultipartUpload Mounted a difficulty the place all elements had been beforehand learn into gateway reminiscence on the identical time throughout a completion operation.
This launch removes some legacy mechanisms. With the introduction of session token v2 in v0.43.0, help for entry packing containers utilizing session token v1 and bearer-based tokens has been fully eliminated. Backward compatibility code for storing bucket configuration, CORS, tags, and notification metadata as devoted NeoFS objects has additionally been eliminated. This storage scheme was migrated to container attributes in v0.42.0. Object-level ACL help has additionally been eliminated because of recognized bugs, outsized EACL tables, and unresolved points.
These removals include sensible improve necessities. Customers with outdated bearer token credentials should regenerate their credentials utilizing the authmate instrument. In case you have not but migrated your bucket metadata from conventional object-based storage codecs, it’s best to improve to v0.44.0, which robotically handles the migration, earlier than continuing to v0.45.0.
Releases for each gateways might be discovered on the hyperlinks under.
https://github.com/nspcc-dev/neofs-rest-gw/releases/tag/v0.18.0
https://github.com/nspcc-dev/neofs-s3-gw/releases/tag/v0.45.0
