Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS not parsing #220

Open
klempie opened this issue Nov 6, 2016 · 0 comments
Open

TLS not parsing #220

klempie opened this issue Nov 6, 2016 · 0 comments

Comments

@klempie
Copy link

klempie commented Nov 6, 2016

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

user daemon
pidfile /var/run/sniproxy.pid
listener 0.0.0.0 80 {
      proto http
      access_log {
                filename /var/log/sniproxy/http_access.log
                priority notice
      }
}
listener 0.0.0.0 443 {
      proto tls
      access_log {
                filename /var/log/sniproxy/https_access.log
                priority notice
      }
}
table {
     (hulu|huluim)\.com *
     netflix\.com *
     ip2location\.com *
     timeslive\.co.za *
}
error_log {
     filename /var/log/sniproxy/sniproxy_error.log
     priority notice
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant