Hi Yann,
Sorry for the late reply. For some reason your email wasn't
delivered until now :-(
Do you know which headers is sent back to the client with the
401 response?
The client expects either WWW-Authenticate with 401 or
Proxy-Authenticate with 407 - and will throw an
IOException: Invalid
Hi,
Thank you for trying the new HTTP client!
I believe both issues described here might have been fixed.
At least JDK 11 should let you specify your own authorization
header, and I have verified that a simple GET request works
with an inline executor.
However there could be some other issues e
On Java 10.0.1 (build 10.0.1+10), the incubating HttpClient has 2 behaviors
that I believe are problematic and should either be fixed or documented to
better highlight their limitations.
The first concerns customized Authorization headers. From what I
understand, Authorization headers outside of "
Hello everyone,
seems I was called out by name so wanted to confirm that point is being
understood correctly.
(tracking this thread with much anticipation, but don’t want to add more
noise, discussion seems pretty healthy so far!).
Rossen clarifies my point very well, but to confirm it myself as w
Hello,
I tried to use the incubator/httpclient to use a rest API. This API use non
standard header and a json web token for authentication. This API return 401
status when the token is missing.
Currently ( java version "10" 2018-03-20 ) the response processing end with :
```
java.io.IOException
Hello
I'm trying to new use new shiny httpclient from JDK10. Code is pretty
simple. I use synchronous HTTP call form multiple threads:
private final HttpClient httpClient = HttpClient.newBuilder()
.executor(Utils.newFixedThreadPoolExecutor(1, "HttpClient"))
.build();
private JsonOb
