-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat: local support for presigned url #476
Conversation
const body = req.body | ||
? JSON.stringify(req.body) | ||
: await getBody(req); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks weird. Why are you stringifying the body?
Also, when I hacked around this, I had to be careful about handling OPTIONS pre-flight requests when calling put on the front end.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ohh, yeah, OPTIONS is a good point. I think I'll just need to let unhandled methods pass through to the normal handler.
I was stringifying here because this logic was originally AFTER the JSON body parser, but now it is before so I can remove this logic.
}; | ||
} | ||
|
||
public decodeAsyncUrlKey( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand the name "decode async url key"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol, I let the AI name this and forgot to change it.
Closes #341