Conditional in HttpConnection.cs seems redundant?

[omajid]

runtime/src/libraries/System.Net.HttpListener/src/System/Net/Managed/HttpConnection.cs

Lines 519 to 533 in 7e316e2

	if (_chunked && _context.Response.ForceCloseChunked == false)
	{
	// Don't close. Keep working.
	_reuses++;
	Unbind();
	Init();
	BeginReadRequest();
	return;
	}
	_reuses++;
	Unbind();
	Init();
	BeginReadRequest();
	return;

The same code is executed if the conditional is true or false. Is the conditional supposed to do something different?

[ghost]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

runtime/src/libraries/System.Net.HttpListener/src/System/Net/Managed/HttpConnection.cs

Lines 519 to 533 in 7e316e2

	if (_chunked && _context.Response.ForceCloseChunked == false)
	{
	// Don't close. Keep working.
	_reuses++;
	Unbind();
	Init();
	BeginReadRequest();
	return;
	}
	_reuses++;
	Unbind();
	Init();
	BeginReadRequest();
	return;

The same code is executed if the conditional is true or false. Is the conditional supposed to do something different?

Author:	omajid
Assignees:	-
Labels:	area-System.Net.Http
Milestone:	-

[stephentoub]

This code originally came from Mono, and history in this repo has those two blocks always being the same; looking in mono/mono, it goes back upwards of 15 years, and arrived like this after multiple refactorings. I'm not sure what the original intent was, but we can delete the duplication now.

[CarnaViire]

Would you like to submit a PR @omajid?

From triage perspective, putting it to Future. We would welcome the contribution. Thanks!