Bug: timestamp is not honored in /attributes/restSearch

[hazcod]

Expected behavior

When I issue the following HTTP POST request to /attributes/restSearch, I get old attributes:

{
    "returnFormat": "json",
    "timestamp": "2023-01-02",
    "published": 1,
    "page": 0,
    "limit": 100
}

Which will return e.g.

{
    "id": "1855",
    "event_id": "4",
    "object_id": "0",
    "object_relation": null,
    "category": "Other",
    "type": "comment",
    "to_ids": false,
    "uuid": "cd70624e-79a2-4066-aaec-fc511e0b1xxx",
    "timestamp": "1573635698",
    "distribution": "5",
    "sharing_group_id": "0",
    "comment": "Imported from STIX header description",
    "deleted": false,
    "disable_correlation": false,
    "first_seen": null,
    "last_seen": null,
    "value": "FOO (November 1 to November 8)",
    "Event":
    {
    }
}

And this timestamp translates into Nov 13 2019 09:01:38 which is 3 years ago.

Actual behavior

Get old attributes, regardless of timestamp parameter.

Steps to reproduce

Send any request with a timestamp parameter set to e.g. yesterday.

Version

2.4.166

Operating System

Unsure

Operating System version

Unsure

PHP version

Unsure

Browser

HTTP

Browser version

No response

Relevant log output

No response

Extra attachments

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[hazcod]

I also tried setting timestamp to 24h but with no difference.

[hazcod]

Related to lack of content-type