You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, let me say from the outset that my networks knowledge is pretty bad, more so wrt to protocols. But I've done a lot of googling and testing and I think the problem is correctly identified.
It seems to be forwarding requests correctly for http requests from the client. So calls to timeslive.co.za, ip2location.com and hulu.com return pages. But as soon as I try secure pages like netflix.com, I get ERR_RESPONSE_HEADERS_TRUNCATED.
When I go to the https access log, I get the following kind of response. There are loads of these same attempts in the space of a second or so.
Firstly, let me say from the outset that my networks knowledge is pretty bad, more so wrt to protocols. But I've done a lot of googling and testing and I think the problem is correctly identified.
It seems to be forwarding requests correctly for http requests from the client. So calls to timeslive.co.za, ip2location.com and hulu.com return pages. But as soon as I try secure pages like netflix.com, I get ERR_RESPONSE_HEADERS_TRUNCATED.
When I go to the https access log, I get the following kind of response. There are loads of these same attempts in the space of a second or so.
2016-11-02 08:25:11 AAA:BBB:CCC:DDD:PORT -> 0.0.0.443 -> NONE [] 7/7 bytes tx 219/438 bytes rx 0.000 seconds
Thanks in advance.
Setup:
Ubuntu 15.04 in the cloud.
/etc/sniproxy.conf
The text was updated successfully, but these errors were encountered: