2015-11-11 16:25 GMT+01:00 Mark Thomas :
> Since I had everything set up, I took a look at the network traffic and
> all I was seeing was a single request (over h2) for drawboard.xhtml.
>
> I did some digging and found the Chrome was reporting errors in that
> page because no content-type was set.
On 10/11/2015 21:57, Mark Thomas wrote:
> On 10/11/2015 21:54, Rémy Maucherat wrote:
>> 2015-11-10 22:34 GMT+01:00 Mark Thomas :
>>
>>> Just a quick update on the issues Violeta reported with 9.0.x, HTTP/2
>>> and Windows.
>>>
>>> I can repeat the Chrome + WebSocket == failure result
>>>
>>
>> What
On 10/11/2015 21:54, Rémy Maucherat wrote:
> 2015-11-10 22:34 GMT+01:00 Mark Thomas :
>
>> Just a quick update on the issues Violeta reported with 9.0.x, HTTP/2
>> and Windows.
>>
>> I can repeat the Chrome + WebSocket == failure result
>>
>
> What is the expected test result ? If using ALPN, chr
2015-11-10 22:34 GMT+01:00 Mark Thomas :
> Just a quick update on the issues Violeta reported with 9.0.x, HTTP/2
> and Windows.
>
> I can repeat the Chrome + WebSocket == failure result
>
What is the expected test result ? If using ALPN, chrome connects using
HTTP/2, which then has no way to upgr
Just a quick update on the issues Violeta reported with 9.0.x, HTTP/2
and Windows.
I can repeat the Chrome + WebSocket == failure result
For ( Chrome | FF ) + stockticker, I see a long pause before any content
appears, then I get about 30 lines, then lines start appearing
individually as expected
