nspcc-dev/neofs-http-gw
1
0
Fork 0
mirror of https://github.com/nspcc-dev/neofs-http-gw.git synced 2026-03-01 04:29:08 +00:00
Code Issues 8 Projects Packages Wiki Activity

Error 404 (Not Found) for object with attributes right after POST #71

New issue
Closed
opened 2025-12-28 17:36:01 +00:00 by sami · 8 comments
sami commented 2025-12-28 17:36:01 +00:00
Owner
Copy link

Originally created by @e7506c on GitHub (Jul 21, 2022).

I have setup with several storage nodes in the cloud. When I try to GET objects right after POST using attributes, I've got 404 error.

I've got 404 error for GET object right after POST when using GET with attributes
If I put some sleep after POST (5 seconds), GET returns object fine.

NOTE: issue is not reproduced with DevEnv.

Expected Behavior

Object returns with GET right after POST.

Current Behavior

I've got 404 error for GET object right after POST when using GET with attributes
If I put some sleep after POST (5 seconds), GET returns object fine.

Steps to Reproduce (for bugs)

  1. Create container using neofs-cli:
COMMAND: 'neofs-cli --rpc-endpoint 172.26.162.59:8080 container create --wallet /tests/TemporaryDir//441e1266-1008-4e1e-925d-936930f902ee.json --config /tests/neofs_cli_configs/empty_passwd.yml --policy "REP 1 IN X CBF 1 SELECT 1 FROM * AS X" --basic-acl 0x0FBFBFFF    --await'
OUTPUT:
 container ID: 4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3
awaiting...
container has been persisted on sidechain
  1. Put object with attributes using http gate:
REQUEST: 'http://172.26.162.59:8888/upload/4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3'
RESPONSE:
 {'object_id': '6Y4MgyGwBWBYWrRbzXdxycj2uJqfBpCgjWZc92HnVwty', 'container_id': '4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3'}
  1. Try to get this object right after that using http gate:
REQUEST: 'http://172.26.162.59:8888/get/4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3/6Y4MgyGwBWBYWrRbzXdxycj2uJqfBpCgjWZc92HnVwty'
RESPONSE:
 200
  1. Try to get this object with attributes:
http://172.26.162.59:8888 "GET /get_by_attribute/4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3/fileName/simple_obj_filename

Got error:

request: /get_by_attribute/4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3/fileName/simple_obj_filename,
                response: object not found

if wait some time (up to 5 seconds). GET returns fine:

REQUEST: 'http://172.26.162.59:8888/get_by_attribute/4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3/fileName/simple_obj_filename'
RESPONSE:
 200
Originally created by @e7506c on GitHub (Jul 21, 2022). I have setup with several storage nodes in the cloud. When I try to GET objects right after POST using attributes, I've got 404 error. I've got 404 error for GET object right after POST when using GET with attributes If I put some sleep after POST (5 seconds), GET returns object fine. NOTE: issue is not reproduced with DevEnv. ## Expected Behavior Object returns with GET right after POST. ## Current Behavior I've got 404 error for GET object right after POST when using GET with attributes If I put some sleep after POST (5 seconds), GET returns object fine. ## Steps to Reproduce (for bugs) 1. Create container using neofs-cli: ``` COMMAND: 'neofs-cli --rpc-endpoint 172.26.162.59:8080 container create --wallet /tests/TemporaryDir//441e1266-1008-4e1e-925d-936930f902ee.json --config /tests/neofs_cli_configs/empty_passwd.yml --policy "REP 1 IN X CBF 1 SELECT 1 FROM * AS X" --basic-acl 0x0FBFBFFF --await' OUTPUT: container ID: 4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3 awaiting... container has been persisted on sidechain ``` 2. Put object with attributes using http gate: ``` REQUEST: 'http://172.26.162.59:8888/upload/4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3' RESPONSE: {'object_id': '6Y4MgyGwBWBYWrRbzXdxycj2uJqfBpCgjWZc92HnVwty', 'container_id': '4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3'} ``` 3. Try to get this object right after that using http gate: ``` REQUEST: 'http://172.26.162.59:8888/get/4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3/6Y4MgyGwBWBYWrRbzXdxycj2uJqfBpCgjWZc92HnVwty' RESPONSE: 200 ``` 4. Try to get this object with attributes: ``` http://172.26.162.59:8888 "GET /get_by_attribute/4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3/fileName/simple_obj_filename ``` Got error: ``` request: /get_by_attribute/4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3/fileName/simple_obj_filename, response: object not found ``` if wait some time (up to 5 seconds). GET returns fine: ``` REQUEST: 'http://172.26.162.59:8888/get_by_attribute/4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3/fileName/simple_obj_filename' RESPONSE: 200 ```
sami 2025-12-28 17:36:01 +00:00
  • closed this issue
  • added the
    bug
    U3
         labels
sami commented 2025-12-28 17:36:01 +00:00
Author
Owner
Copy link

@alexvanin commented on GitHub (Jul 22, 2022):

Two questions:

  1. Is it reproduced when HTTP Gateway configured with single endpoint in the peer section of config? nspcc-dev/neofs-http-gw@a2d667acf9/config/config.yaml (L19-L38)
  2. Is it reproduced with NeoFS CLI by invoking object put and object get commands?
@alexvanin commented on GitHub (Jul 22, 2022): Two questions: 1. Is it reproduced when HTTP Gateway configured with _single_ endpoint in the peer section of config? https://github.com/nspcc-dev/neofs-http-gw/blob/a2d667acf9482a72b7f348494f27d96d36526057/config/config.yaml#L19-L38 2. Is it reproduced with NeoFS CLI by invoking `object put` and `object get` commands?
sami commented 2025-12-28 17:36:01 +00:00
Author
Owner
Copy link

@e7506c commented on GitHub (Jul 27, 2022):

Sorry for a long replay.

Not sure if I mentioned this clearly, but there is no problem with getting object by id using HTTP gate right after put. The problem with getting object by attribute using HTTP.

Anyway, I tried with your suggestions. My config file looks like this:

before:

HTTP_GW_LISTEN_ADDRESS=0.0.0.0:8888
HTTP_GW_LOGGER_LEVEL=info
HTTP_GW_CONNECT_TIMEOUT=60s
HTTP_GW_REQUEST_TIMEOUT=300s
HTTP_GW_KEEPALIVE_TIMEOUT=300s
HTTP_GW_KEEPALIVE_TIME=120s
HTTP_GW_METRICS=False
HTTP_GW_PPROF=False
HTTP_GW_VERBOSE=false
HTTP_GW_KEEPALIVE_PERMIT_WITHOUT_STREAM=True
HTTP_GW_CONN_TTL=1h
HTTP_GW_REBALANCE_TIMER=5m
HTTP_GW_PEERS_0_ADDRESS=node1.neofs:8080
HTTP_GW_PEERS_0_WEIGHT=100
HTTP_GW_PEERS_1_ADDRESS=node2.neofs:8080
HTTP_GW_PEERS_1_WEIGHT=1
HTTP_GW_PEERS_2_ADDRESS=node3.neofs:8080
HTTP_GW_PEERS_2_WEIGHT=1
HTTP_GW_PEERS_3_ADDRESS=node4.neofs:8080
HTTP_GW_PEERS_3_WEIGHT=1

after the change:

HTTP_GW_WALLET_PASSPHRASE=
HTTP_GW_LISTEN_ADDRESS=0.0.0.0:8888
HTTP_GW_LOGGER_LEVEL=info
HTTP_GW_CONNECT_TIMEOUT=60s
HTTP_GW_REQUEST_TIMEOUT=300s
HTTP_GW_KEEPALIVE_TIMEOUT=300s
HTTP_GW_KEEPALIVE_TIME=120s
HTTP_GW_METRICS=False
HTTP_GW_PPROF=False
HTTP_GW_VERBOSE=false
HTTP_GW_KEEPALIVE_PERMIT_WITHOUT_STREAM=True
HTTP_GW_CONN_TTL=1h
HTTP_GW_REBALANCE_TIMER=5m
HTTP_GW_PEERS_0_ADDRESS=node1.neofs:8080
HTTP_GW_PEERS_0_WEIGHT=100

and yes, issue is still reproduced.

  1. No, it seems like I don't see this kind of issue with object put and object get using NeoFS CLI.
@e7506c commented on GitHub (Jul 27, 2022): Sorry for a long replay. Not sure if I mentioned this clearly, but there is no problem with getting object by id using HTTP gate right after put. The problem with getting object by attribute using HTTP. Anyway, I tried with your suggestions. My config file looks like this: before: ```HTTP_GW_WALLET_PASSPHRASE= HTTP_GW_LISTEN_ADDRESS=0.0.0.0:8888 HTTP_GW_LOGGER_LEVEL=info HTTP_GW_CONNECT_TIMEOUT=60s HTTP_GW_REQUEST_TIMEOUT=300s HTTP_GW_KEEPALIVE_TIMEOUT=300s HTTP_GW_KEEPALIVE_TIME=120s HTTP_GW_METRICS=False HTTP_GW_PPROF=False HTTP_GW_VERBOSE=false HTTP_GW_KEEPALIVE_PERMIT_WITHOUT_STREAM=True HTTP_GW_CONN_TTL=1h HTTP_GW_REBALANCE_TIMER=5m HTTP_GW_PEERS_0_ADDRESS=node1.neofs:8080 HTTP_GW_PEERS_0_WEIGHT=100 HTTP_GW_PEERS_1_ADDRESS=node2.neofs:8080 HTTP_GW_PEERS_1_WEIGHT=1 HTTP_GW_PEERS_2_ADDRESS=node3.neofs:8080 HTTP_GW_PEERS_2_WEIGHT=1 HTTP_GW_PEERS_3_ADDRESS=node4.neofs:8080 HTTP_GW_PEERS_3_WEIGHT=1 ``` after the change: ``` HTTP_GW_WALLET_PASSPHRASE= HTTP_GW_LISTEN_ADDRESS=0.0.0.0:8888 HTTP_GW_LOGGER_LEVEL=info HTTP_GW_CONNECT_TIMEOUT=60s HTTP_GW_REQUEST_TIMEOUT=300s HTTP_GW_KEEPALIVE_TIMEOUT=300s HTTP_GW_KEEPALIVE_TIME=120s HTTP_GW_METRICS=False HTTP_GW_PPROF=False HTTP_GW_VERBOSE=false HTTP_GW_KEEPALIVE_PERMIT_WITHOUT_STREAM=True HTTP_GW_CONN_TTL=1h HTTP_GW_REBALANCE_TIMER=5m HTTP_GW_PEERS_0_ADDRESS=node1.neofs:8080 HTTP_GW_PEERS_0_WEIGHT=100 ``` and yes, issue is still reproduced. 2. No, it seems like I don't see this kind of issue with `object put` and `object get` using NeoFS CLI.
sami commented 2025-12-28 17:36:01 +00:00
Author
Owner
Copy link

@KirillovDenis commented on GitHub (Aug 8, 2022):

@e7506c

  1. Try to get this object with attributes: http://172.26.162.59:8888 "GET /get_by_attribute/4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3/fileName/simple_obj_filename

Did you explicitly set the fileName attribute by using X-Attribute-fileName header during object uploading? By default the object name is stored in FileName attribute

@KirillovDenis commented on GitHub (Aug 8, 2022): @e7506c > 4. Try to get this object with attributes: ```http://172.26.162.59:8888 "GET /get_by_attribute/4wkA8cFmv9Ks17EVzcDqJQgz2yvfDTfXAu14QmfzmSF3/fileName/simple_obj_filename ``` Did you explicitly set the `fileName` attribute by using `X-Attribute-fileName` header during object uploading? By default the object name is stored in `FileName` attribute
sami commented 2025-12-28 17:36:01 +00:00
Author
Owner
Copy link

@KirillovDenis commented on GitHub (Aug 12, 2022):

@e7506c

No, it seems like I don't see this kind of issue with object put and object get using NeoFS CLI.

Actually you should try to reproduce this with neofs-cli object search --filters filters.json rather than neofs-cli object get
Sample of filters.json:

[{"matchType":"STRING_EQUAL","key":"FileName","value":"simple_obj_filename"}]
@KirillovDenis commented on GitHub (Aug 12, 2022): @e7506c > No, it seems like I don't see this kind of issue with object put and object get using NeoFS CLI. Actually you should try to reproduce this with `neofs-cli object search --filters filters.json` rather than `neofs-cli object get` Sample of `filters.json`: ```json [{"matchType":"STRING_EQUAL","key":"FileName","value":"simple_obj_filename"}] ```
sami commented 2025-12-28 17:36:01 +00:00
Author
Owner
Copy link

@KirillovDenis commented on GitHub (Aug 25, 2022):

@vdomnich-yadro @anikeev-yadro
Could you please reproduce this bug and check: https://github.com/nspcc-dev/neofs-http-gw/issues/176#issuecomment-1207730692, https://github.com/nspcc-dev/neofs-http-gw/issues/176#issuecomment-1213076488

@KirillovDenis commented on GitHub (Aug 25, 2022): @vdomnich-yadro @anikeev-yadro Could you please reproduce this bug and check: https://github.com/nspcc-dev/neofs-http-gw/issues/176#issuecomment-1207730692, https://github.com/nspcc-dev/neofs-http-gw/issues/176#issuecomment-1213076488
sami commented 2025-12-28 17:36:01 +00:00
Author
Owner
Copy link

@anikeev-yadro commented on GitHub (Sep 1, 2022):

@KirillovDenis reproduced steps :

filters.json
echo [{"matchType":"STRING_EQUAL","key":"FileName","value":"object1662034723"}]

Put object by http:

curl -F file=@/home/anikeev/neofs/object1662034723;filename=object1662034723 http://172.26.163.38:8888/upload/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1
{
        "object_id": "79hZqhqN6UdtgwHfCeBGaPaKA6BgNRHCWT1QLpZzGj8v",
        "container_id": "8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1"
}

Get object by http right after put - OK:

wget http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/FileName/object1662034723
--2022-09-01 15:18:44--  http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/FileName/object1662034723
Connecting to 172.26.163.38:8888... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1048576 (1.0M) [application/octet-stream]
Saving to: ‘object1662034723.1’
object1662034723.1                                                   47%[============================================================================>                                                                                      ] 488.68K  1.17MB/s
object1662034723.1                                                  100%[==================================================================================================================================================================>]   1.00M  1.50MB/s    in 0.7s
2022-09-01 15:18:44 (1.50 MB/s) - ‘object1662034723.1’ saved [1048576/1048576]

Search object right after put - OK:

./neofs-cli object search --filters filters.json --rpc-endpoint 172.26.163.38:8080 --wallet wallet.json --cid 8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1
Enter password >
Found 1 objects.
79hZqhqN6UdtgwHfCeBGaPaKA6BgNRHCWT1QLpZzGj8v

Versions:

NeoFS HTTP Gateway
Version: v0.23.0-6-g035f043-dirty
GoVersion: go1.18.4
@anikeev-yadro commented on GitHub (Sep 1, 2022): @KirillovDenis reproduced steps : filters.json ```echo [{"matchType":"STRING_EQUAL","key":"FileName","value":"object1662034723"}]``` Put object by http: ``` curl -F file=@/home/anikeev/neofs/object1662034723;filename=object1662034723 http://172.26.163.38:8888/upload/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1 { "object_id": "79hZqhqN6UdtgwHfCeBGaPaKA6BgNRHCWT1QLpZzGj8v", "container_id": "8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1" } ``` Get object by http right after put - OK: ``` wget http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/FileName/object1662034723 --2022-09-01 15:18:44-- http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/FileName/object1662034723 Connecting to 172.26.163.38:8888... connected. HTTP request sent, awaiting response... 200 OK Length: 1048576 (1.0M) [application/octet-stream] Saving to: ‘object1662034723.1’ object1662034723.1 47%[============================================================================> ] 488.68K 1.17MB/s object1662034723.1 100%[==================================================================================================================================================================>] 1.00M 1.50MB/s in 0.7s 2022-09-01 15:18:44 (1.50 MB/s) - ‘object1662034723.1’ saved [1048576/1048576] ``` Search object right after put - OK: ``` ./neofs-cli object search --filters filters.json --rpc-endpoint 172.26.163.38:8080 --wallet wallet.json --cid 8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1 Enter password > Found 1 objects. 79hZqhqN6UdtgwHfCeBGaPaKA6BgNRHCWT1QLpZzGj8v ``` Versions: ``` NeoFS HTTP Gateway Version: v0.23.0-6-g035f043-dirty GoVersion: go1.18.4 ```
sami commented 2025-12-28 17:36:01 +00:00
Author
Owner
Copy link

@anikeev-yadro commented on GitHub (Sep 1, 2022):

I think the root cause is in fileName attribute insted of FileName.
Because I have tried to wait some time between get oject by attribute with name fileName. But original issue was not reploruced.

curl -F file=@/home/anikeev/neofs/object1662036782;filename=object1662036782 http://172.26.163.38:8888/upload/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1
{
        "object_id": "6UESd7WABjjjmynF4Hxc35xGXtD4DYusgoHdDbDX5Ma1",
        "container_id": "8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1"
}
wget http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782
--2022-09-01 15:53:03--  http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782
Connecting to 172.26.163.38:8888... connected.
HTTP request sent, awaiting response... 404 Not Found
2022-09-01 15:53:03 ERROR 404: Not Found.

wget http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/FileName/object1662036782
--2022-09-01 15:53:03--  http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/FileName/object1662036782
Connecting to 172.26.163.38:8888... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1048576 (1.0M) [application/octet-stream]
Saving to: ‘object1662036782.1’
object1662036782.1                                                  100%[==================================================================================================================================================================>]   1.00M  2.91MB/s    in 0.3s
2022-09-01 15:53:03 (2.91 MB/s) - ‘object1662036782.1’ saved [1048576/1048576]

anikeev@NB-1670:~/neofs$ wget http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782
--2022-09-01 15:53:39--  http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782
Connecting to 172.26.163.38:8888... connected.
HTTP request sent, awaiting response... 404 Not Found
2022-09-01 15:53:40 ERROR 404: Not Found.

anikeev@NB-1670:~/neofs$ wget http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782
--2022-09-01 15:55:55--  http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782
Connecting to 172.26.163.38:8888... connected.
HTTP request sent, awaiting response... 404 Not Found
2022-09-01 15:55:55 ERROR 404: Not Found.

anikeev@NB-1670:~/neofs$ wget http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782
--2022-09-01 15:57:26--  http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782
Connecting to 172.26.163.38:8888... connected.
HTTP request sent, awaiting response... 404 Not Found
2022-09-01 15:57:26 ERROR 404: Not Found.
@anikeev-yadro commented on GitHub (Sep 1, 2022): I think the root cause is in ```fileName``` attribute insted of ```FileName```. Because I have tried to wait some time between get oject by attribute with name ```fileName```. But original issue was not reploruced. ``` curl -F file=@/home/anikeev/neofs/object1662036782;filename=object1662036782 http://172.26.163.38:8888/upload/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1 { "object_id": "6UESd7WABjjjmynF4Hxc35xGXtD4DYusgoHdDbDX5Ma1", "container_id": "8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1" } wget http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782 --2022-09-01 15:53:03-- http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782 Connecting to 172.26.163.38:8888... connected. HTTP request sent, awaiting response... 404 Not Found 2022-09-01 15:53:03 ERROR 404: Not Found. wget http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/FileName/object1662036782 --2022-09-01 15:53:03-- http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/FileName/object1662036782 Connecting to 172.26.163.38:8888... connected. HTTP request sent, awaiting response... 200 OK Length: 1048576 (1.0M) [application/octet-stream] Saving to: ‘object1662036782.1’ object1662036782.1 100%[==================================================================================================================================================================>] 1.00M 2.91MB/s in 0.3s 2022-09-01 15:53:03 (2.91 MB/s) - ‘object1662036782.1’ saved [1048576/1048576] anikeev@NB-1670:~/neofs$ wget http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782 --2022-09-01 15:53:39-- http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782 Connecting to 172.26.163.38:8888... connected. HTTP request sent, awaiting response... 404 Not Found 2022-09-01 15:53:40 ERROR 404: Not Found. anikeev@NB-1670:~/neofs$ wget http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782 --2022-09-01 15:55:55-- http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782 Connecting to 172.26.163.38:8888... connected. HTTP request sent, awaiting response... 404 Not Found 2022-09-01 15:55:55 ERROR 404: Not Found. anikeev@NB-1670:~/neofs$ wget http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782 --2022-09-01 15:57:26-- http://172.26.163.38:8888/get_by_attribute/8q3Hyxh8ohuAcD5DEWB7xpE3TxB8FFNhEd3U8yYQtbb1/fileName/object1662036782 Connecting to 172.26.163.38:8888... connected. HTTP request sent, awaiting response... 404 Not Found 2022-09-01 15:57:26 ERROR 404: Not Found. ```
sami commented 2025-12-28 17:36:02 +00:00
Author
Owner
Copy link

@alexvanin commented on GitHub (Sep 13, 2022):

Cannot reproduce on latest master. Reopen in case of any further issues with it.

@alexvanin commented on GitHub (Sep 13, 2022): Cannot reproduce on latest master. Reopen in case of any further issues with it.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27.0
v0.26.0
v0.25.1
v0.25.0
v0.24.0
v0.23.0
v0.22.0
v0.21.0
v0.20.0
v0.19.0
v0.18.0
v0.17.0
v0.16.1
v0.16.1-pre
v0.16.0
v0.16.0-pre
v0.15.2
v0.15.2-pre
v0.15.1
v0.15.1-pre
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.0
v0.12.1
v0.12.0
v0.12.0-rc.3
v0.12.0-rc.2
v0.12.0-rc.1
v0.9.0-pre-1
v0.8.1
v0.8.0
v0.7.1
v0.7.0
v0.5.0
v0.4.0
v0.3.2
v0.3.1
v0.3.0
v0.2.8
v0.2.7
Labels
Clear labels   
I1

   
I3

   
I4

   
S2

   
S3

   
S4

   
U2

   
U2

   
U3

   
U4

   
blocked

   
bug

   
config

   
documentation

   
enhancement

   
go

   
good first issue

   
help wanted
No labels
I1
I3
I4
S2
S3
S4
U2
U2
U3
U4
blocked
bug
config
documentation
enhancement
go
good first issue
help wanted
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-http-gw#71
No description provided.