:lady_beetle: Describe the bug
Hello! I'm using apprise api (great project by the way)
I'm running into an issue with adding attachments that are signed s3 urls. I was able to successfully send an attachment with the smtp mode but the name was "attachment.001" instead of the file name. It looks like when sending the url you can add a query parameter of a "name" from what I can see in the code. That does not work and gives that error. Without that, I get that strange name instead of the s3 file name.
:bulb: Screenshots and Logs
If I try that though I get the following error:
apprise-1 | 2024-08-01 16:34:35,041 [WARNING] django: NOTIFY - 127.0.0.1 - Bad attachment: apprise.attachment.http.AttachHTTP.init() got multiple values for keyword argument 'name'
:computer: Your System Details:
OS: Running through docker and apprise-api
Python Version: Same as docker container for apprise-api
:crystal_ball: Additional context
Add any other context about the problem here.
Not sure why you closed this off, i'll gladly investigate it. I'll need more details as to how you're creating a curl or web request to the Apprise API to get this error message though.
:mega: Notification Service(s) Impacted SMTP
:lady_beetle: Describe the bug Hello! I'm using apprise api (great project by the way)
I'm running into an issue with adding attachments that are signed s3 urls. I was able to successfully send an attachment with the smtp mode but the name was "attachment.001" instead of the file name. It looks like when sending the url you can add a query parameter of a "name" from what I can see in the code. That does not work and gives that error. Without that, I get that strange name instead of the s3 file name.
:bulb: Screenshots and Logs
If I try that though I get the following error:
apprise-1 | 2024-08-01 16:34:35,041 [WARNING] django: NOTIFY - 127.0.0.1 - Bad attachment: apprise.attachment.http.AttachHTTP.init() got multiple values for keyword argument 'name'
:computer: Your System Details:
:crystal_ball: Additional context Add any other context about the problem here.