Skip to content

Empty weak etag is supposed to match? #261

@achingbrain

Description

@achingbrain

This test sends an empty weak etag (which should not match anything) but expects a 304 back, so expects it to match:

Name: GET for /ipfs/ dir listing with matching weak ETA in If-None-Match returns 304 Not Modified

Error: Status code is not 304. It is 200

Expected Request:
"method": "GET",
"path": "/ipfs/bafybeib3ffl2teiqdncv3mkz4r23b5ctrwkzrrhctdbne6iboayxuxk5ui/root2/root3/",
"headers": {
  "If-None-Match": "W/\"\""
}

Actual Request:

GET /ipfs/bafybeib3ffl2teiqdncv3mkz4r23b5ctrwkzrrhctdbne6iboayxuxk5ui/root2/root3/ HTTP/1.1
Host: 127.0.0.1:3334
User-Agent: ipfs/gateway-conformance/dev
If-None-Match: W/""
Accept-Encoding: gzip

Expected Response:

{
  "statusCode": 304
}


Actual Response:

HTTP/1.1 200 OK
Content-Length: 53
Accept-Ranges: bytes
...

The test tries to send a CID but it seems to be empty - is this a bug?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions