This message was deleted.

I can’t say for sure, but if you are getting a behavior change in the way the content is being served from your endpoint. Then I would guess it has something to do with you adding those new response headers. Perhaps there was some header being added by default, that is no longer sent because you customized it? If the content was previously served as JSON, but now comes across as base-64 encoded text. Perhaps you need to explicitly set the

Content-Type

header? in the response? There are many moving parts that could also be the culprit here. But hopefully that helps.

Thank you for your response, I noticed that the content from my GET/POST/... calls was served in JSON again when I removed the OPTIONS endpoints and keept the headesr I set. So I compared the headers I get when there is this endpoint in my api and when there is not, and as expected in both cases the headers are the same (and both have Content-Type set to application/json, even when the body is in base 64). So now I don’t really know why the addition of a new endpoint could change the way the others are serving data 🤔