Google’s False Start gets a real stop

Google security researcher Adam Langley has announced that Google is abandoning attempts to bring its secure connection speed-up False Start technology to HTTP/S enabled sites. False Start was introduced in Google's Chrome open source browser and attempted to speed up secure connections by reducing the number of round-trip passes involved in setting up an SSL connection – this was achieved by getting the client to send the "Finished" message and first ApplicationData message in one packet, rather than sending "Finished", waiting for a response and then sending the first ApplicationData message. False Start could reduce the time taken to start connections by 30 per cent. Read more...