You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've updated the widget to the latest version (the most recent 'master' commit), but I noticed that the store sync method (when 'Upload' button is clicked) uses 'PUT' which causes the method to fail / behave erratically (e.g. web server may respond with a 500 or a 405, or just fail silently).
Unfortunately I can't seem to locate the particular change in the source (through comparing the latest version that I have vs the latest version).
The text was updated successfully, but these errors were encountered:
I'm not sure I get this - your problem is that the widget uses the PUT method and the server doesn't support it? I think that the PUT method was default before the update also. Anyway, it is possible to set alternative method like POST.
I'm not sure which method should be default. The difference between POST and PUT is IMHO in immutability - PUT is immutable, POST is not.
That's strange, I haven't done any special configuration using the previous version, and it defaults to POST. The reason I noticed, is that after upgrading, the server started returning 404's as I haven't defined a PUT endpoint. I've updated the server-side methods to PUT but the behaviour is erratic.
How would I set the default method to POST? Do I need to specify the uploader specifically and pass on the options?
PS: At the moment I use POST for create and PUT for update operations. But, thanks for the tip about POST vs PUT, there's certainly a lot of differing opinion about REST verb usages and I'll need to do a bit more research.
I've updated the widget to the latest version (the most recent 'master' commit), but I noticed that the store sync method (when 'Upload' button is clicked) uses 'PUT' which causes the method to fail / behave erratically (e.g. web server may respond with a 500 or a 405, or just fail silently).
Unfortunately I can't seem to locate the particular change in the source (through comparing the latest version that I have vs the latest version).
The text was updated successfully, but these errors were encountered: