Description:
------------
fopen fails(sometimes, as heavier system loads it will be successful, and less load fails) web requests using http/https when behind cheap routers with content filtering on.  This is due to how php sends headers.  

how php runs.
php_stream_write("GET / HTTP/1.0\r\n");
php_stream_write("Host: www.hostname.com\r\n");
php_stream_write("\r\n");

This potentially forces 3 packet sends where cheaper hardware cannot reconstruct the request entirely.  Since content filters need to know the host, the hardware fails after it gets the "GET" and hangs.

Changing the code to a minimum of

php_stream_write("GET / HTTP/1.0\r\nHost: www.hostname.com\r\n");
php_stream_write("\r\n");

this will force the GET and the Host line to be in the same packet.  Enough for cheap hardware to see it and handle appropriately.

also, opening a socket and handling the http protocol manually, works fine.

The attached patch, works, but would like to test more to make sure it doesn't cause any other problems.

Test script:
---------------
$web = fopen("http://www.google.com/", "r"); // need cheap hardware with content filtering turned on



Expected result:
----------------
On cheap hardware, it will timeout and not perform the request.