Why should I inject IHttpContextAccessor as a Singleton : <p>In all examples that i've seen of <code>IHttpContextAccessor</code> injection, it is set as a Singleton.</p>

<p>Examples: </p>

<p><a href="https://stackoverflow.com/questions/38184583/how-to-add-ihttpcontextaccessor-in-the-startup-class-in-the-di-in-asp-net-core-1">How to add IHttpContextAccessor in the Startup class in the DI in ASP.NET Core 1.0?</a>
<a href="https://stackoverflow.com/questions/39131925/injecting-ihttpcontextaccessor-into-applicationdbcontext-asp-net-core-1-0">Injecting IHttpContextAccessor into ApplicationDbContext ASP.NET Core 1.0</a>
<a href="https://stackoverflow.com/questions/40303982/net-core-ihttpcontextaccessor-issue">.NET Core IHttpContextAccessor issue</a></p>

<p>I find it kinda weird, since <code>HttpContext</code> really looks like something that maps to requests. Wouldn't <code>AddScoped</code> be more appropriate in this case?</p>

<p>Is Singleton really the recomended way? Am I not seeeing something?</p>
