Middleware backchannels should set User-Agent #52

Tratcher · 2014-08-26T17:40:11Z

Many of the security middleware have HttpClient instances they use for back-channel communication. Each middleware that does this should set the User-Agent header to facilitate tracking and debugging.

Recommended pattern: "ASP.NET Security (Twitter)"

Tratcher added enhancement labels Aug 26, 2014

Tratcher mentioned this issue Aug 26, 2014

#38 - Port the Twitter middleware from katana #51

Merged

Tratcher self-assigned this Sep 15, 2014

Tratcher added 1 - Ready and removed 0 - Backlog labels Sep 16, 2014

Tratcher added 2 - Working and removed 1 - Ready labels Sep 24, 2014

Tratcher mentioned this issue Sep 24, 2014

Set a default user-agent for the OAuth backchannel. #68

Merged

Tratcher added 3 - Done and removed 2 - Working labels Oct 2, 2014

Tratcher modified the milestone: 1.0.0-alpha4 Oct 2, 2014

Tratcher added this to the 1.0.0-beta1 milestone Oct 20, 2014

Tratcher closed this as completed Oct 20, 2014

Tratcher removed the 3 - Done label Oct 20, 2014

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Middleware backchannels should set User-Agent #52

Middleware backchannels should set User-Agent #52

Tratcher commented Aug 26, 2014

Middleware backchannels should set User-Agent #52

Middleware backchannels should set User-Agent #52

Comments

Tratcher commented Aug 26, 2014