I received this email the other day:
Hello Google HTTP(S) Load Balancing Customer, > We’re writing to let you know about a change to the behavior of HTTP(S) > Load Balancers > <https://www.google.com/appserve/mkt/p/AFnwnKV6zRxIMF-67TmW7W5HvnDdf-QAcingmd5i49SjY2PNzfS3NJMTGC8kkgPg4HrPsLrxNG6_La2vPBkoj0naADyEkZefRHpWf5kKwcN7xfh9uo8DXUqNbr4> > > that is being rolled out gradually, beginning September 30, 2019. We are > making this change to standardize HTTP(S) load balancer behavior across > HTTP/1.1 and more modern protocols, including HTTP/2 and QUIC. > What do I need to know? > After September 30, HTTP(S) Load Balancers will convert HTTP/1.1 header > names to lowercase in the request and response directions; header values > will not be affected. I would prefer not do delegate the responsibility of my HTTP header casing to GCP. Who knows, perhaps this code will live somewhere else one day? Is there a way I could "easily" lowercase all the HTTP headers I send? e.g. w.Header().Set("x-sync-token", csrf.Token(r)) Will be sent as *X-Sync-Token* What do you guys do? Do you think it's necessary to update the headers sent as long as the clients are case insensitive? Best, Martin -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/be3bf673-5ac1-4a01-a39c-325480254734%40googlegroups.com.
