Add value to HttpStatusCode enum: TooManyRequests (=HTTP 429)

[kwaazaar]

This statuscode is often returned when quotas or throttling limits are being applied to an API. This is often done using an API platform such as Azure API Management or Nginx. Since API's are gaining popularity and more companies are introducing these limits, this statuscode will appear more often in real live scenarios and therefore deserves a representation in this enum.

See the commit on my fork (1 file change): kwaazaar/corefx@f52cd49

[davidsh]

Pushing to Future. We do not plan to take any API change for 2.0 release. Doing so requires we push the Http contract out of NETStandard2.0.

Also, see #15650. There are other status codes we would like to add to the HttpStatusCode enum type as well. The 429 status code is already included in that issue #15650.

[davidsh]

Dupe of #15650.

[stephentoub]

Doing so requires we push the Http contract out of NETStandard2.0.

What does this mean? We can add to the .NET Core API surface area without impacting netstandard2.0.

[davidsh]

What does this mean? We can add to the .NET Core API surface area without impacting netstandard2.0.

Yes, we could add it to just .NET Core 2.0 surface and not to NETStandard20. But there is a lot of work in API changes including packaging, testing, etc.

We are prioritizing reliability and other high-impact things at this point for .NET Core 2.0. Adding API surface area like this is not high priority and so will be deferred.

[karelz]

@davidsh ... we could add it to just .NET Core 2.0 surface and not to NETStandard20.

FYI: That is the default way we add any new APIs in CoreFX these days. We do not push NetStandard contracts. Especially given that we plan to stop shipping Desktop packages.
BTW: While we push many issues to Future as they are not "must-have" for 2.0, we still take community contributions (PRs) for Future issues as well.