Recently, I and a few others reported that CORS headers had gone missing. This was then fixed. Last night everything was working great, and now this morning I’m getting alerts that it is broken again.
Can we please have CORS headers allowed through again?
Hmm, that is a bit weird then, as you state in your other post that it stopped working and then was working again two days later.
https://www.wix.com/corvid/forum/community-discussion/corvid-stripping-cors-headers
Maybe it was just down to those Wix Devs doing routine maintenance and they broke it somehow (does happen with Google and Apple Devs and many others!), although it would be nice if somebody could reply back to yourself and say the reason or that it was at least fixed.
However, nothing should have been altered in the first place really, unless we have missed something in the Corvid update notes etc.
If it had changed, then you would have at least expected it to be mentioned in the API reference for Wix HTTP Functions. https://www.wix.com/corvid/reference/wix-http-functions.html#options
Plus, that page is linked to Mozilla article about it, which was last updated on 9th April 2019, so if ot had changed, it would have at lest been mentioned here.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/OPTIONS#Identifying_allowed_request_methods
Anyways, enough blabbering on now, this shouldn’t affect your working, however have a quick read of this page too.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP)
The headers are back again. I have a few open support requests with Wix for more information.
I agree that it was likely an update to the Wix platform that happened late last night or this morning that broke it again. Same breaking change twice in such quick succession is a bit surprising. I’m working on adding some additional and independent monitoring so I can detect the issue much more quickly.
The main concern I have with this particular bug, is if Wix is planning to restrict this type of functionality in the future and hasn’t communicated that with us yet via their API docs or Changelog. Being able to set CORS headers is key to my use case. If this won’t be allowed, I would greatly appreciate a heads up as I’ll have to find a different platform to use.
Overall, what Wix has done with Corvid is amazing. The functionality and customization options they are providing is fantastic and is a reason why I have begun recommending Wix to my peers. The fact we are essentially getting a managed Lambda platform and nosql DB is wonderful. However, without CORS headers, the usefulness of Corvid drops down when you are considering transitioning to a new Wix site gradually or trying to integrate with other related websites that are not on the Wix platform.
For those who stumble across this one, see more detailed discussion and history of CORS headers being removed at the following posts:
https://www.wix.com/corvid/forum/community-discussion/bug-access-control-allow-origin-not-being-sent
https://www.wix.com/corvid/forum/community-discussion/corvid-stripping-cors-headers
Hi Nick. Can you please share the site it happened to you?