nginx: Include CORS configuration for custom BlueOS services

[rafaellehmkuhl]

This patch allows external applications, like Cockpit, to use the service to store configuration data.

[CLAassistant]

All committers have signed the CLA.

[Williangalvani]

have you tried going through /bag/ ? nginx should handle it

[rafaellehmkuhl]

have you tried going through /bag/ ? nginx should handle it

Tried, yes. No success:

Access to fetch at 'http://192.168.0.12/bag/v1.0/get/cockpit' from origin 'http://localhost:5173' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

[rafaellehmkuhl]

@Williangalvani @patrickelectric any suggestion on this one?

[Williangalvani]

can you try adding both of these to the "server" block?
https://github.com/bluerobotics/BlueOS/blob/master/core/tools/nginx/nginx.conf#L132-L135

[Williangalvani]

or maybe we just need proxy_hide_header on /bag

[rafaellehmkuhl]

or maybe we just need proxy_hide_header on /bag

No luck.

I really think the server has to add CORS policy.
NGINX can do so much. In terms of delivering the content or not is up to the actual server (FastAPI/Starlette/Uvicorn).