The /list endpoint in JustLog does not correctly filter logs by the userid parameter. Instead of returning logs specific to the provided user ID, it returns logs for the entire channel.
Steps to Reproduce
Make a GET request to https://justlog.alb11747.com/list?channel=fobm4ster&userid=31062476.
The /list endpoint should filter logs based on the userid parameter when provided, similar to how it filters based on the username and channelid parameters.
Actual Behavior
The /list endpoint ignores the userid parameter and returns logs for the entire channel.
It appears that the userid parameter is not being properly handled in the query logic for the /list endpoint. A review of the parameter parsing and filtering logic may be necessary to resolve this issue.
Description
The
/list
endpoint in JustLog does not correctly filter logs by theuserid
parameter. Instead of returning logs specific to the provided user ID, it returns logs for the entire channel.Steps to Reproduce
Make a GET request to
https://justlog.alb11747.com/list?channel=fobm4ster&userid=31062476
.Sample Output:
Make a GET request to
https://justlog.alb11747.com/list?channelid=31062476&userid=31062476
.Sample Output:
Make a GET request to
https://justlog.alb11747.com/list?username=fobm4ster&channelid=31062476
.Sample Output:
Expected Behavior
The
/list
endpoint should filter logs based on theuserid
parameter when provided, similar to how it filters based on theusername
andchannelid
parameters.Actual Behavior
The
/list
endpoint ignores theuserid
parameter and returns logs for the entire channel.Additional Information
ghcr.io/gempir/justlog:latest@sha256:b414506c7da33c958b831f29d0d7fc947a17bd9f55c09b79d05020b1c53765d4
Possible Solution
It appears that the
userid
parameter is not being properly handled in the query logic for the/list
endpoint. A review of the parameter parsing and filtering logic may be necessary to resolve this issue.