Skip to content
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.

Response allows setting StatusCode and ReasonPhrase after response was started #805

Closed
Tratcher opened this issue May 5, 2016 · 0 comments
Closed

Response allows setting StatusCode and ReasonPhrase after response was started #805

Tratcher opened this issue May 5, 2016 · 0 comments
Assignees
@cesarblum
Labels
3 - Done bug
Milestone
1.0.0

Comments

@Tratcher
Copy link
Member

Tratcher commented May 5, 2016

From @pakrym on May 5, 2016 21:36

This works:

await context.Response.WriteAsync("Hello");
context.Response.StatusCode = 2;

It should prevent setting status code the same way Headers, Cookies, ContentType do.

/cc @Tratcher

Copied from original issue: aspnet/HttpAbstractions#626
@Tratcher Tratcher mentioned this issue May 5, 2016
Closed
@muratg muratg added this to the 1.0.0 milestone May 9, 2016
cesarblum pushed a commit that referenced this issue May 20, 2016
Throw when setting Frame.StatusCode after response has already started (
c6865f0 
#805).
@cesarblum cesarblum mentioned this issue May 20, 2016
Merged
cesarblum pushed a commit that referenced this issue May 20, 2016
Throw when setting Frame.StatusCode after response has already started (
fb95b3d 
#805).
cesarblum pushed a commit that referenced this issue May 24, 2016
Throw when setting Frame.StatusCode or Frame.ReasonPhrase after respo…
ac3c740 
…nse has already started (#805).
cesarblum pushed a commit that referenced this issue May 24, 2016
Throw when setting Frame.StatusCode or Frame.ReasonPhrase after respo…
ac05fc7 
…nse has already started (#805).
cesarblum pushed a commit that referenced this issue May 24, 2016
Throw when setting Frame.StatusCode or Frame.ReasonPhrase after respo…
3f4e232 
…nse has already started (#805).
@cesarblum cesarblum changed the title Response allows setting StatusCode after body was started Response allows setting StatusCode and ReasonPhrase after response was started May 24, 2016
@Tratcher Tratcher mentioned this issue Aug 11, 2016
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@cesarblum cesarblum

Labels
3 - Done bug
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
3 participants
@cesarblum @muratg @Tratcher