A customer has reported an issue where appconfig is no longer accepting the x-ms-useragent header. This prevents users from using appconfig in the browser.
This was fixed in #217 but appears to have regressed and is missing again. I see this list of headers when doing an OPTIONS request against my own appconfig server (x-ms-useragent is not present):
$ curl -XOPTIONS -vv https://[app config server].azconfig.io
Headers:
< Access-Control-Allow-Headers: DNT, X-CustomHeader, Keep-Alive, User-Agent, X-Requested-With, If-Modified-Since, Cache-Control, Content-Type, Authorization, x-ms-client-request-id, x-ms-content-sha256, x-ms-date, host, Accept, Accept-Datetime, Date, If-Match, If-None-Match, Sync-Token, x-ms-return-client-request-id, ETag, Last-Modified, Link, Memento-Datetime, x-ms-retry-after, x-ms-request-id, WWW-Authenticate
Customer issue: https://github.com/Azure/azure-sdk-for-js/issues/7529
This could be a regression due to recent changes for VNET support. We will fix it.
cc: @MSGaryWang
Any idea on when this will be corrected? I would like to give an update to management on when this feature will be available again.
The next train of deployment will be next week, so by the end of next week, I hope the fix can be deployed to all regions if everything goes smoothly.
Are we still on track of this being deployed this week?
Yes
On Mon, Mar 9, 2020 at 9:22 AM edmclinn notifications@github.com wrote:
Are we still on track of this being deployed this week?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Azure/AppConfiguration/issues/277?email_source=notifications&email_token=ABAIE346BR6XJ26HS5AGH7TRGUCS5A5CNFSM4K4LH3M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOHNBEQ#issuecomment-596562066,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAIE37LJD4VN5RCULKXEBTRGUCS5ANCNFSM4K4LH3MQ
.
The deployment has completed for all regions. This should work now.
Most helpful comment
This could be a regression due to recent changes for VNET support. We will fix it.
cc: @MSGaryWang