* Fix request absolute URI handling

When a request uses an absolute request target with scheme and host
parts, the current absoluteURI() method simply concatenates the Host
header value and the request target URI. For example, with the following
request:

```
GET http://www.example.com:1234/path HTTP/1.1
Host: www.example.com:1234
```

The result of HttpServerRequest.absoluteURI() would then be:

`http://www.example.com:1234www.example.com:1234/path`

With this change, when the request target is absolute, only the path
(and query) are added to the Host value:

`http://www.example.com:1234/path`

Fixes #2830

* Update vertx-web/src/main/java/io/vertx/ext/web/impl/ForwardedParser.java

---------

Co-authored-by: Thierry Monney <[email protected]>

…eption

See #2844

To prevent from a recursive update of the same key in the externalSolvingRefs, avoid computeIfAbsent and continue walking the references path only when an uncompleted future has effectively been put in the map.

Signed-off-by: Thomas Segismont <[email protected]>

…StateException"

This reverts commit 34d4481.

…eption (#2845)

See #2844

To prevent from a recursive update of the same key in the externalSolvingRefs, avoid computeIfAbsent and continue walking the references path only when an uncompleted future has effectively been put in the map.

Signed-off-by: Thomas Segismont <[email protected]>