Ok, I've since discovered that there's an nginx proxy in front of my
service that is adding the header.
Sorry for the false alarm. :(
Problem resolved.
On Tuesday, December 6, 2016 at 5:30:12 PM UTC-5, paul.h....@gmail.com
wrote:
>
> We have a simple http service running using the net/http package and I
> tried setting the Access-Control-Allow-Origin header value as in:
>
> w.Header().Set("Access-Control-Allow-Origin", "*")
>
> and when I do so the client side gets an error: "The
> 'Access-Control-Allow-Origin' header contains multiple values"
>
> So it seems somewhere else the request origin is already added to the
> header although I can't find any mention of this in the docs.
> What's the correct method for setting this header value so that it
> overrides what's there already?
>
> Thanks for any pointers.
>
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
