otp.git/lib/inets/src/http_lib, branch maint-20

inets: Gracefully handle bad headers

2018-05-22T16:07:50+00:00

max_headers operated on the individual header length instead of
the total length of all headers. Also headers with empty keys are
now discarded.

inets: work around http_uri:parse Dialyzer warning in uri_SUITE.erl:274

2018-03-06T09:31:58+00:00

Addresses https://github.com/erlang/otp/pull/1724#discussion_r172442753

Current `http_uri:parse/2` implementation intends that ["non-fun
scheme_validation_fun works as no option
passed"](https://github.com/erlang/otp/blob/OTP-20.2.4/lib/inets/test/uri_SUITE.erl#L271-L274).

inets: refine types and doc of http_uri:parse options

2018-03-05T11:36:17+00:00

inets: export types documented for http_uri module

2018-03-05T10:56:02+00:00

Also:

* Reuse type `inet:port_number()` in `http_uri` code and doc;

* Do not imply that http_uri module can properly handle UTF-8 encoded
  binaries, while it can't.

* Enrich function specifications in http_uri module;

* Fix http_uri doc re missing type definition for `Scheme`.

inets: Restore old behavior when parsing "+"

2017-09-06T11:20:21+00:00

"+" is part of sub-delims according to RFC 3986 and shall not be
converted to space.

Update copyright year

2017-06-14T13:36:21+00:00

add binary string support to http_uri functions

2017-05-05T15:48:30+00:00

Update copyright year

2017-05-04T13:42:21+00:00

Omit port from Host header on redirect to well-known port

2017-03-17T08:35:49+00:00

ERL-316, as part of 19.3, adds the port number to the Host header
upon automatic redirection. The port number is included even if it
is a well-known port (80, 443). This is different from the
behaviour of most HTTP clients, as well as httpc's own for new
requests.

The added port number can lead to problems such as this one, where
the request signature assumes the client will not send the :443
suffix on redirection to an https URL:
https://github.com/nerves-project/nerves/issues/96

I was unable to add a test case, since that would require a server
on a well-known port, but I manually verified that the GitHub/S3
signing issue was indeed resolved with this patch.

Update copyright-year

2016-12-07T12:15:31+00:00