100 requests from website
OR
100 requests from cors-proxy
Customers submit to SeaTable via cors-proxy web-forms end-point.
No difference in resources for SeaTable right? Server still handles 100 requests?
But customer not forced to run redundant proxy server to fix rewrite CORS headers for web-forms end points. Or would love to know why not simply allow submit directly?
