User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
Hello Joakim,
Thank you! That makes sense. But does that mean that Jetty9
implements some backward compatibility feature to simulate a Host
header? The same code works with HTTP/2 on Jetty9.
Cheers,
Silvio
On 9/21/20 7:00 PM, Joakim Erdfelt
wrote:
Ah, HTTP/2.
Well, HTTP/2 doesn't have a "Host" header, it has an
":authority" header.
I am using HTTP/2. It is a plain HTTPS GET from the browser
(Chromium) using a domain name that is mapped to local
(127.0.0.1) and that matches one of the certificates in my
key store.
I dumped request.getHeaderNames and there is no Host header
in there. But the same thing works with Jetty9 although I
did not dump the headers with that one.
Kind regards,
Silvio
On 9/21/20 6:18 PM, Joakim Erdfelt wrote:
What version of HTTP? (HTTP/1.0, HTTP/1.1, or
HTTP/2)
Also, what does the entire request look like? (eg:
if HTTP/1.1, what's the request line plus headers?)
I am testing our application that runs on embedded
Jetty9 with (also
embedded) Jetty 10 beta. It fails very early because
our application
calls request.getHeader("Host") which appears to
return null. I used the
same embedding code which works flawlessly with
Jetty9. Is there
something I am doing wrong?
