On Monday 15 August 2016 14:32:46 Max Meyer wrote:
[..]
> But now the server won't do HTTP/2 anymore, it falls back to HTTP/1.1.
> I tried the same with an Apache webserver and it worked fine, so I guess
> it is not a general problem with the chosen cipher.
>
> Any ideas on what could be the prob
Hi,
> for a test environment I successfully set up an nginx webserver (1.11.2)
> with HTTP/2.
>
> But for further tests I need to decrypt traffic with wireshark using the
> servers private key.
The way to do this is to use keyfile from your browser, so wireshark is aware
of the symmetric key
Hi,
for a test environment I successfully set up an nginx webserver (1.11.2)
with HTTP/2.
But for further tests I need to decrypt traffic with wireshark using the
servers private key.
For that I need to disable forward secrecy (since it is only a test
environment security is not an issue)
On Sun, Aug 14, 2016 at 08:03:21PM -0400, Larry Martell wrote:
> On Tue, Aug 9, 2016 at 10:35 PM, Richard Stanway
> wrote:
Hi there,
> I have some requests that can take a long time to return - the users
> can request huge amount of data to be pulled from very large database
> tables with comple
