This message was deleted.
# helpdesk
s
This message was deleted.
a
How about Url encoding?
a
I do not manage this from my side, file names (and dates) are generated from egress service side, the problem is only with {time}
a
The problem is that the character cannot be used with the s3 file name, so I suggested a way to solve the problem. URL encoding seems to be a way to upload files to s3 including such characters, and other methods include removing the character in question or changing the file name to a value allowed by s3 file name. sorry for my poor English.
d
I've opened an issue for this. we'll fix this shortly: https://github.com/livekit/egress/issues/164
👍 2