Hi Chris,
When I use curl, I also get the same response via HTTP, not HTTP/2.
curl --http2 -k -v -g -6 https://\[::1\]:8443
I think I leave it for now. But thanks for your support.
Cheers,
Sven
On 7/6/16, 3:01 AM, "Christopher Schultz" wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven,
On 6/6/16 9:34 AM, Sven Schleier wrote:
> Hi Mark,
>
> Thanks for this hint. My Tomcat is actually reachable from external
> via HTTP/2. When I try to connect via the official domain I can
> connect via HTTP/2 over SSL (h2), but not locally via
Thanks for helping out Mark. If I have some time I will dig deeper into the
issue, for now it’s ok.
On 6/6/16, 9:51 PM, "Mark Thomas" wrote:
>On 06/06/2016 14:34, Sven Schleier wrote:
>> Hi Mark,
>>
>> Thanks for this hint. My Tomcat is actually reachable from external via
>> HTTP/2. When I
On 06/06/2016 14:34, Sven Schleier wrote:
> Hi Mark,
>
> Thanks for this hint. My Tomcat is actually reachable from external via
> HTTP/2. When I try to connect via the official domain I can connect via
> HTTP/2 over SSL (h2), but not locally via localhost. Tomcat is listening on
> all interfac
Hi Mark,
Thanks for this hint. My Tomcat is actually reachable from external via HTTP/2.
When I try to connect via the official domain I can connect via HTTP/2 over SSL
(h2), but not locally via localhost. Tomcat is listening on all interfaces, and
HTTP connections on localhost are working, but
On 02/06/2016 01:23, Sven Schleier wrote:
> True, you are right. Do you have any suggestion or sample configuration that
> should work you can share, or anyone else?
https://www.youtube.com/watch?v=oCFwgMvouis
You can use 8.5.x where you see 9.0.x.
Setting
org.apache.coyote.http2.level = FINE
i
Hi Chris,
➜ apache-tomcat-8.5.2 nghttp -v https://127,0.0.1:8443
[ 0.000] Connected
[ERROR] HTTP/2 protocol was not selected. (nghttp2 expects h2)
Some requests were not processed. total=1, processed=0
I am not getting more information. Same behavior with hostname
Thanks and cheers,
Sven
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sven,
On 6/1/16 8:23 PM, Sven Schleier wrote:
> True, you are right. Do you have any suggestion or sample
> configuration that should work you can share, or anyone else?
$ nghttp -v https://127.0.0.1:8443/
??
What if you use the hostname of
True, you are right. Do you have any suggestion or sample configuration that
should work you can share, or anyone else?
On 1/6/16, 9:13 PM, "Mark Thomas" wrote:
>On 01/06/2016 14:07, Sven Schleier wrote:
>> Yes. That’s possible. I am just missing the “HTTP/1.1 101 Switching
>> Protocols” so i
On 01/06/2016 14:07, Sven Schleier wrote:
> Yes. That’s possible. I am just missing the “HTTP/1.1 101 Switching
> Protocols” so it’s not switching to HTTP/2.
You'll only get that if you try to use HTTP/2 over a non-TLS channel.
When using TLS, ALPN is used to negotiate the protocol.
Mark
>
>
Yes. That’s possible. I am just missing the “HTTP/1.1 101 Switching Protocols”
so it’s not switching to HTTP/2.
On 1/6/16, 7:04 PM, "Mark Thomas" wrote:
>On 01/06/2016 03:16, Sven Schleier wrote:
>> Hi mailinglist,
>>
>> I just want to play around with the new HTTP/2 implementation of Tomcat
On 01/06/2016 03:16, Sven Schleier wrote:
> Hi mailinglist,
>
> I just want to play around with the new HTTP/2 implementation of Tomcat
> 8.5.2 Beta. The tomcat instance is up and running and the h2 support is
> activated, according to the log during startup:
>
> 01-Jun-2016 01:57:52.544 INFO [ma
Hi mailinglist,
I just want to play around with the new HTTP/2 implementation of Tomcat 8.5.2
Beta. The tomcat instance is up and running and the h2 support is activated,
according to the log during startup:
01-Jun-2016 01:57:52.544 INFO [main]
org.apache.coyote.http11.AbstractHttp11Protocol.
13 matches
Mail list logo
