How to improve security for Memberstack components by switching from GET to POST requests? Answered
Is there any reason to not use the POST request method? All the Memberstack components default to GET but wouldn't it be a bit more secure to do things like sign-ups or changes to a server via POST?
Curious what you guys think. Thanks!
Comments
4 comments
Still wondering about this... Does it make a difference for Memberstack? I am assuming no.
Noah Reeves can you explain more about this?
We are using POST for signups / updates.
It seemed to me that whenever I dropped in Memberstack components (ie signup, login) they all defaulted to GET. I have since switched them to POST and was curious if it made a difference or if Memberstack handles that setting on their end.
I believe Memberstack doesn't use the Webflow setting of GET/POST you put and rather just handles it securely in their own way. But I really am not 100% confident that that is the case. Would love for someone from Memberstack to chime in.
I can confirm that the GET/POST settings you see in Webflow is not used by Memberstack.
Adjusting that in Webflow makes no difference.
Please sign in to leave a comment.