![]() ![]() However the header is not doing this job in this case (more like appending to it).Īre there any caddyfile directives that override the ‘Access-Control-Allow-Origin’ header on the reverse proxy? Thank you. (let’s say, the /api/foo/bar responses with Access-Control-Allow-Origin, while /api/a/b does not) Locating which of these URLs are carrying the header is a bit painstaking, and hard-coding them in the caddyfile lacks flexibility.Īs described in caddy docs, the default behaviour of setting a header directive is to “overwrite any existing field of the same name”. But the problem is, only a few of the backend apis are responding with the CORS header. Adding CORS to an existing backend is something easy to do with caddy, however, this time chrome is giving me this error message: 'Access-Control-Allow-Origin' header contains multiple values '*, *'Īdmittedly, there would be no need to set Access-Control-Allow-Origin in caddyfile if the backend is already doing so. I’m designing the frontend for an existing spring app, and CORS is required in this case. ![]() The 'Access-Control-Allow-Origin' header contains multiple values '*, *', My complete Caddyfile or JSON config: has been blocked by CORS policy: Service/unit/compose file: version: '3'ĭ. Header add Access-Control-Allow-Origin '' Header add Access-Control. Ubuntu 20.04 LTS 圆4, Docker version 19.03.8, Docker-compose version 1.25.0 b. I have an html5 application written in javascript and html hosted on an apache 2.2 server. ![]() V2.2.1 h1:Q62GWHMtztnvyRU+KPOpw6fNfeCD3SkwH7SfT1Tgt2c= 2. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |