I am including appwrite using the following in my client side html
<script src="https://cdn.jsdelivr.net/npm/appwrite@14.0.1"></script>
I have a weird scenario playing out where in I have a python based function, where I dumped just before the endpoint returns and the output is showing
{'body': '{"error": "Method Not Allowed - POST", "Scenario": "42d0d764-a729-41e5-a8f4-1c1b7ec0b5ec"}', 'status': 405, 'headers': { 'Content-Type': 'application/json', 'Access-Control-Allow-Origin': 'https://mysubdomain.mydomaincom/', 'Access-Control-Allow-Methods': 'POST, OPTIONS', 'Access-Control-Allow-Headers': 'Content-Type, Authorization' } }
which is exactly what it needs to be.
But on web client (plan JS) side I have the attached JS code and I am seeing the following output
POST REST API responded with status: 200 POST REST API responded with status text: POST REST API headers:: [Array(2)] POST REST API response data:: {error: 'Method Not Allowed - POST', Scenario: '42d0d764-a729-41e5-a8f4-1c1b7ec0b5ec'}
How is it that the body data is intact, but the status got switched from 405 to 200?
Recommended threads
- Any way to temporarily bypass the email ...
Hey guys, any way to bypass the email verification to use the accounts again? i need to recover some projects that due to recent changes have been stopped, and ...
- Create a new paid tier
Current pricing seems reasonable enough about what is someone getting for 25$. But for some people most of these resouces are getting wasted. Like the bandwidt...
- [Bug] Appwrite Auth User Prefs
User prefs are decoded as blank although there are plenty of data and add preference button not working in this case