-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Communication]: Always use x-ms-date for Hmac #15807
[Communication]: Always use x-ms-date for Hmac #15807
Conversation
/azp run js - communication-sms - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think we'll need to re-record recordings?
/azp run js - communication-chat - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-chat - tests
I'm trying to figure that out. It seems the recording only contains response headers not request headers. The Hmac header change is not reflected in the recorded sessions |
No pipelines are associated with this pull request. |
/azp run js - communication-identity - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
oh yes, only the browser ones will have it, but the header was only different in node |
/azp run js - communication-phonenumbers - tests |
No pipelines are associated with this pull request. |
/azp run js - communication-phone-numbers - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-network-traversal - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-phone-numbers - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-phone-numbers - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-phone-numbers - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-sms - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-identity - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-chat - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-network-traversal - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-network-traversal - tests |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
/azp run js - communication-chat - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-identity - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-sms - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - communication-phone-numbers - tests |
1 similar comment
/azp run js - communication-phone-numbers - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.