Useful helper methods for common http scenarios

[davidfowl]

I was looking at golang's standard library and they have a pretty beefy http package https://golang.org/pkg/net/http. Here are a few that seemed interesting:

https://golang.org/pkg/net/http/#Request.WriteProxy https://golang.org/pkg/net/http/#ServeContent https://golang.org/pkg/net/http/#Request.SetBasicAuth (sorry @blowdart :smile: ) https://golang.org/pkg/net/http/#DetectContentType https://golang.org/pkg/net/http/#MaxBytesReader

[blowdart]

I'm surprised you're not saying sorry about DetectContentType - that is way more concerning than Basic Auth, although at least they're not picking some of the more dangerous ones.

[Tratcher]

• WriteProxy is for clients, not servers.
• Some subset of ServeContent might be useful, especially for last modified, range requests, if-modified-since, etc.. I'd make them specify the content-type though. MVC already handles many of these, correct? Static files implements them, but that implementation wouldn't be generally applicable because it relies on SendFile.
• People want MaxBytesReader, there were several 3rd party implementations for WebApi2 and OWIN/Katana.

[davidfowl]

WriteProxy is for clients, not servers.

Not sure what you mean. If you look at their API it writes to a "Stream" equivalent. This might be any network stream that is proxying requests over to another server even. It doesn't need to map directly to HttpClient.

MVC already handles many of these, correct? Static files implements them, but that implementation wouldn't be generally applicable because it relies on SendFile.

Moving building blocks into HttpAbstractions would be great. Even simpler versions that didn't rely on MVC intrinsics would be a good start.

[muratg]

@davidfowl Moving out of V1. If you think this is a MUST, bring it back