I was looking into google.com\'s Net activity in firebug just because I was curious and noticed a request was returning \"204 No Content.\"
It turns out that a 204 N
Google is using this to detect whether the device is online or in captive portal.
Shill, the connection manager for Chromium OS, attempts to detect services that are within a captive portal whenever a service transitions to the ready state. This determination of being in a captive portal or being online is done by attempting to retrieve the webpage http://clients3.google.com/generate_204. This well known URL is known to return an empty page with an HTTP status 204. If for any reason the web page is not returned, or an HTTP response other than 204 is received, then shill marks the service as being in the portal state.
Here is the relevant explanation from the Google Chrome Privacy Whitepaper:
In the event that Chrome detects SSL connection timeouts, certificate errors, or other network issues that might be caused by a captive portal (a hotel's WiFi network, for instance), Chrome will make a cookieless request to http://www.gstatic.com/generate_204 and check the response code. If that request is redirected, Chrome will open the redirect target in a new tab on the assumption that it's a login page. Requests to the captive portal detection page are not logged.
More info: http://www.chromium.org/chromium-os/chromiumos-design-docs/network-portal-detection