Bug:Should clean the context.Items cache

[mangshao]

[commonsensesoftware]

The properties stored in HttpContext.Items is not a cache. They only store information about the current request. Per the documentation, the "collection is available from the start of an HttpRequest and is discarded at the end of each request".

I'm not sure what the issue or expected action is here.

[mangshao]

You can check this blog

[commonsensesoftware]

Unfortunately, I don't know what language that is nor what it says.

From what I can discern, it appears that you're encountering an issue with using the error page in conjunction with API versioning. Unfortunately, this is currently by design and is a limitation in how end of route middleware work. Both API versioning and the exception handler try to put themselves at the end of MVC pipeline. I've engaged with the ASP.NET team, but there needs to be some enhancements to the routing infrastructure in order to improve the experience.

I'm not entirely sure why a service would want an error page, but this is a topic that has come up a few times recently. I suggest taking a look at #221. I provided a workable solution that should help.

[commonsensesoftware]

I was able to use a translator on your blog post. I suggest you follow the thread and guidance in #221. That will get you the desired result without changing the IApiVersionRoutingPolicy. This issue is not related to items in the HttpContext. I can provide lengthy explanation if you like.

[commonsensesoftware]

Any further chance of this particular issue being a problem has been resolved by #280, which refactors to use a feature instead. There's a reasonable chance this was also related, at least in part, to #306. These changes have been realized in the 3.0 release. Thanks for the feedback.