Looking at the wireshark logs the request and responses look exactly the same, there's an outgoing HTTP GET and an incoming 200 OK inn both cases, each time this is post proxy. Using a wget for the same url downloads the key as required instantly (no timeout/fault) Using Wireshark I can see the actual HTTP request done for this is Gpg: keyserver recieve failed: keyserver error Gpg -debug-all -v -ignore-time-conflict -no-options -no-default-keyring -no-auto-check-trustdb -trust-model always -keyring /etc/apt/trusted.gpg -primary-keyring /etc/apt/trusted.gpg -keyserver hkp://:80 -recv-keys 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62 http.time is, as Christian said, calculated by Wireshark, but it is calculated in different ways, depending on your preference settings. The command which fails is along the lines of: What looks most promising to me is this: because the SAML process consists of one single https URL being processed I would be able to calculate the response time by calculating time between first packet and last packet. The machine is behind a corporate proxy so all traffic is routed through cntlm, this works fine and has given me few issues so far. I read some posts about http response times but this cant be used for http over tlsv1. Most of this is automatic via puppet but I'm going through the process manually to find where the fault lies. I'm using a virtual machine running Ubuntu 14.04, trying to use apt-keys to add keys for nginx.
0 kommentar(er)
