"Failed to parse API path from client request" error when using the new pin endpoints

[biast12]

https://discord.com/developers/docs/resources/message#get-channel-pins

GET /channels/{channel.id}/pins
PUT /channels/{channel.id}/pins/{message.id}
DELETE /channels/{channel.id}/pins/{message.id}

^Has all been deprecated, and when using the new endpoints↓

GET /channels/{channel.id}/messages/pins
PUT /channels/{channel.id}/messages/pins/{message.id}
DELETE /channels/{channel.id}/messages/pins/{message.id}

Does it give the "Failed to parse API path from client request" error

[biast12]

Also just to add, it's also the endpoints being used for users too

[Erk-]

I don't know what your setup is, but would it be possible for you to test #94?

[biast12]

Yep i'll test it in a few hours when i get home! i use the images / docker, does it have an image?

Should note that i'm using the latest metrics image ghcr.io/twilight-rs/http-proxy:metrics

[biast12]

@Erk- can confirm, it seems to work on #94

[vilgotf]

@biast12 I found a critical bug in my branch, you should rebase to the latest commit.

Rate limit durations were accidentally calculated from the wrong instant, the time before sending the request instead of the time when receiving the response.