Adam Eijdenberg
Adam Eijdenberg
@heikoettelbruecksap - I do agree a compatibility options makes sense, and it looks like others do too, as it exists already here: https://godoc.org/golang.org/x/oauth2#RegisterBrokenAuthHeaderProvider
Perhaps worse, it seems that the output of the well-known config is based on the headers sent in the request. We found this issue when trying to debug a reverse...
Hi @danjahner - I'm struggling a bit to understand how we're expecting this to be used. Our UAA server is serving a certificate signed by a publicly trusted root, which,...
Thanks @danjahner for getting back to me - that seems to be quite an unusual behavior though. That is, I'm glad there's an option to pass your own CA list...
It's a year later, and I'm trying to deploy `credhub` again, and I'm hitting the same bug. We have certificates signed by a publicly trusted CA (Let's Encrypt, this time)....
Thanks @mdelillo
It occurred to me it would be pretty easy to add prepend support at the same time, so I added a commit and test for that, which I think fixes...
@cppforlife I'd be willing to try again with the existing structure. I needed to make a degree of structural change as iterating down the list of tokens wouldn't adapt easily...
Added alternate implementation [here](https://github.com/cppforlife/go-patch/pull/10).
@XenoPhex - as background we run HAProxy co-located and in front of our Gorouters. Last week we experimented with enabling the recently added cache functionality in HAProxy, for the purpose...