Describe the bug
There's several bugs right now dealing with request headers, so those should be fixed. We should not be sending a Content-Type header, but instead the Accept header, and we do not need to ever send the Access-Control header that we had been - that will only ever come from the server, not vice versa. There's also a significant spamming bug related to offline support, which I'm removing temporarily until we can fix it.
To Reproduce
Steps to reproduce the behavior:
Just run Firestore or the realtime database
Expected behavior
When exporting for HTML, most stuff should work, but due to the Content-Type header we're sending, it doesn't properly work with the CORS.
Environment:
OS: HTML
Browser: all
Additional context
This contains the fixes suggested directly by Fales, the maintainer of the entire Godot networking stack, so should be safe to put in.
Describe the bug There's several bugs right now dealing with request headers, so those should be fixed. We should not be sending a Content-Type header, but instead the Accept header, and we do not need to ever send the Access-Control header that we had been - that will only ever come from the server, not vice versa. There's also a significant spamming bug related to offline support, which I'm removing temporarily until we can fix it.
To Reproduce Steps to reproduce the behavior: Just run Firestore or the realtime database
Expected behavior When exporting for HTML, most stuff should work, but due to the Content-Type header we're sending, it doesn't properly work with the CORS.
Environment:
Additional context This contains the fixes suggested directly by Fales, the maintainer of the entire Godot networking stack, so should be safe to put in.