Support object name resolving via tree service #30

New issue

Closed

opened 2023-04-06 12:53:22 +00:00 by alexvanin · 1 comment

alexvanin commented

2023-04-06 12:53:22 +00:00

Owner

HTTP Gateway works great to provide read access to the objects. It is often used together with a S3 Gateway so objects are upload via S3 and available via HTTP. Many web services use AWS S3 to store user's data and provide access to it from the web (e.g. attachment files in the notion.so).

HTTP Gateway now provides a way to access objects using:

bucket name by resolving address in NNS,
object name by searching object via some attribute FileName.

(2) has flaws, because S3 can re-upload object with the same key or store different versions of the same object. HTTP Gateway can't figure it out different versions and uses first FileName attribute match. We can improve it with integration of tree service.

Describe the solution you'd like

Support /get/<bucketname>/<key> scheme and use latest version of the key. Support /get/<cid>/<oid> for backward compatibility.

Describe alternatives you've considered

Use separate endpoint like /s3get/<bucketname>/<key>. However it will be more difficult for nginx proxy to determine which endpoint to use. However regexp might solve this issue?

Additional context

None.

## Is your feature request related to a problem? Please describe. HTTP Gateway works great to provide read access to the objects. It is often used together with a S3 Gateway so objects are upload via S3 and available via HTTP. Many web services use AWS S3 to store user's data and provide access to it from the web (e.g. attachment files in the notion.so). HTTP Gateway now provides a way to access objects using: 1. bucket name by resolving address in NNS, 2. object name by searching object via some attribute `FileName`. (2) has flaws, because S3 can re-upload object with the same key or store different versions of the same object. HTTP Gateway can't figure it out different versions and uses first `FileName` attribute match. We can improve it with integration of tree service. ## Describe the solution you'd like Support `/get/<bucketname>/<key>` scheme and use latest version of the key. Support `/get/<cid>/<oid>` for backward compatibility. ## Describe alternatives you've considered Use separate endpoint like `/s3get/<bucketname>/<key>`. However it will be more difficult for nginx proxy to determine which endpoint to use. However regexp might solve this issue? ## Additional context None.