Open muratbeser opened 8 years ago
I tried it from an other vhost its same result
root@haproxy:~# wget -vd http://192.168.5.1:3990/json/status
DEBUG output created by Wget 1.16 on linux-gnu.
URI encoding = ‘UTF-8’
--2016-01-08 17:28:07-- http://192.168.5.1:3990/json/status
Connecting to 192.168.5.1:3990... connected.
Created socket 4.
Releasing 0x0000000001f9c740 (new refcount 0).
Deleting unused 0x0000000001f9c740.
---request begin---
GET /json/status HTTP/1.1
User-Agent: Wget/1.16 (linux-gnu)
Accept: */*
Host: 192.168.5.1:3990
Connection: Keep-Alive
---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.0 200 OK
Connection: close
Pragma: no-cache
Expires: Fri, 01 Jan 1971 00:00:00 GMT
Cache-Control: no-cache, must-revalidate
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Content-Length: 287
Content-Type: text/javascript
---response end---
200 OK
Length: 287 [text/javascript]
Saving to: ‘status.2’
status.2 100%[============================================================================================================================================================>] 287 --.-KB/s in 0s
Closed fd 4
2016-01-08 17:28:33 (31.6 MB/s) - ‘status.2’ saved [287/287]
Env:
I had this slow response from CoovaJSON on the Kali but not on Windows Xp, so I had some tests and sniffing with Wireshark and I saw saw some TCP Retransmissions request.
And this is really not my thing is there someone can help about issue.
Response time test
Wireshark CoovaJSON HTTP Request
https://gist.github.com/muratbeser/eb87d4346aa8199e4dce