How HttpContext RESPONSE END in ASP.NET Core

Question

I want use mvc System.Web.HttpContext.Current.Response.End(); but trying in mvc core 2 with this code:

 private readonly IHttpContextAccessor _httpContextAccessor;

            public SmsService(IUnitOfWork uow ,IHttpContextAccessor httpContextAccessor) 
            {
                _uow = uow;
                _uow.CheckArgumentIsNull(nameof(_uow));
                _LockIPRequest= uow.Set<LockIPRequest>();
                this._httpContextAccessor = httpContextAccessor;
            }

      _httpContextAccessor.HttpContext.Response.WriteAsync("</body></html>");
      _httpContextAccessor.HttpContext.Response.end();

_httpContextAccessor.HttpContext.Response.end();

end(); doesn't work mvc core dont exits

What do you mean by "it doesn't work"? That is not descriptive. What are you expecting and what is it actually doing? — user47589
– user47589, Commented Nov 7, 2018 at 17:14
Don't use HttpContext or Response like this. ASP.NET Core isn't WebForms and the code used in WebForms isn't needed and won't work. The code posted here doesn't compile or show a complete action. What are you trying to do? Why not return an ActionResult? — Panagiotis Kanavos
– Panagiotis Kanavos, Commented Nov 7, 2018 at 17:37

RonC · Accepted Answer · 2018-11-20 13:30:13Z

23

As has been mentioned in the comments, Response.End does not exist in the ASP.NET Core world.

Instead of Response.End, you should set the response status code like so:

 _httpContextAccessor.HttpContext.Response.StatusCode = StatusCodes.Status200OK;

This won't fully "end" the response. The middleware still gets a chance to run, but by setting the status code, the framework has a way to understand that a response has been provided. You will however be responsible for making sure that your downstream middleware does not output other content in response to the request. Although this is often not a problem.

answered Nov 20, 2018 at 13:30

RonC

34.4k21 gold badges105 silver badges150 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Fairuz Sulaiman Over a year ago

How to apply this instructions on .NET Core 3.1? Which files need to repair? Sorry about my English.

RonC Over a year ago

There is no specific file to change. It’s just that in .net core, including version 3, setting the response status code is the closest thing there is to ending the request. This is true of any response object, regardless of how you obtain access to it ( via middleware, via a controller, etc) hope that helps make it more clear.

Gustavo Mauricio De Barros · Accepted Answer · 2022-08-06 20:22:11Z

2

Now in August 2022, it is possible to call Response.End through the SystemWebAdapters library. I particularly recommend using it only if you are performing a large-scale migration from a .NET Framework project to .NET Core. If you are in a greenfield project, try not to use this library and write your code following the recommendations for ASP.NET Core request/response lifecycle.

answered Aug 6, 2022 at 20:22

Gustavo Mauricio De Barros

3675 silver badges15 bronze badges

2 Comments

Escobar5 Over a year ago

I installed and configured the adapters library, but still no Response.End(), is there anything else that has to be done?

Gustavo Mauricio De Barros Over a year ago

Yes, you need to add .PreBufferRequestStream().BufferResponseStream() in the end of your MapControllerRoute methods.

Collectives™ on Stack Overflow

How HttpContext RESPONSE END in ASP.NET Core

2 Answers 2

2 Comments

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related