Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with Name of S3 Signed URL Attachment #204

Open
dnimon opened this issue Aug 1, 2024 · 1 comment
Open

Issues with Name of S3 Signed URL Attachment #204

dnimon opened this issue Aug 1, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@dnimon
Copy link

dnimon commented Aug 1, 2024

📣 Notification Service(s) Impacted
SMTP

🐞 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.

💡 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'

💻 Your System Details:

  • OS: Running through docker and apprise-api
  • Python Version: Same as docker container for apprise-api

🔮 Additional context
Add any other context about the problem here.

@dnimon dnimon added the bug Something isn't working label Aug 1, 2024
@dnimon dnimon closed this as not planned Won't fix, can't repro, duplicate, stale Aug 8, 2024
@caronc
Copy link
Owner

caronc commented Aug 10, 2024

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.

@caronc caronc reopened this Aug 10, 2024
@caronc caronc transferred this issue from caronc/apprise Aug 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants