News for hackers. Stuff that matters.
Re:HTTP/2.0 — Bad protocol, bad politics by workermonkey on Wednesday January 07, 2015 @09:00AM (#8850485)
On my load balancers it is more like 5-10%. Not terrible, but not trivial either. Also, it multiplies throughout the environment. If you are dealing with PII or financials, everything needs to be encrypted on the wire.

Load balancer decrypts, looks at headers, decides what to do, re-encrypts, down to the app tier, decrypt, respond encrypted, etc. I'm not saying that is a bad thing, but that's why some people get cranky.

Somewhat unrelated, compressed headers in HTTP 2.0 makes sense if you only think about the browser, it saves 'repeated' information. The problem is the LB has to decrypt them every time anyways, so someone still have to do the work, it just isn't on the wire. Server push on the other hand could be awesome for performance (pre-cache the resources for the next page in a flow) but also has the potential for abuse.

Re:HTTP/2.0 — Bad protocol, bad politics by tracker1 on Wednesday January 07, 2015 @03:58PM (#8853258)
Why not just run unencrypted behind the load balancer? Unless they're on wholely different networks, it shouldn't be needed.. SSL termination makes sense at a load balancer, reverse proxy, etc.
Re:HTTP/2.0 — Bad protocol, bad politics by stephen_g on Wednesday January 07, 2015 @06:25PM (#8854027)
Re:HTTP/2.0 — Bad protocol, bad politics by workermonkey on Wednesday January 07, 2015 @05:45PM (#8853851)
PCI.
Re:HTTP/2.0 — Bad protocol, bad politics by magicalist on Wednesday January 07, 2015 @01:13PM (#8852138)
> If you are dealing with PII or financials, everything needs to be encrypted on the wire.

Well I hope you'd be doing that even without HTTP/2...