HTTP request failed! HTTP/1.1 505 HTTP Version Not Supported error

Question

I\'m trying to use file_get_contents() to get the response from a server and this error was encountered. Could someone tell me what is the reason and how to fix

Answer 1

I found the problem, and it was a simple coding error -- missing url encoding.

The reason I didn't notice it at first was because the code was ok before I did some editing, and I'd missed out the urlencode() function before calling the server, which caused a space in the url.

This does seem to be the reason this error occurs for most people. So if you encounter this, use urlencode() on all variables which may contain white space in it's value used as URL parameters. So in the case in my question the fixed code will look like:

$api = "http://smpp5.routesms.com:8080/bulksms/sendsms?username=$username&password=$password&source=$source&destination=$destin&dlr=$dlr&type=$type&message=" . urlencode($message);
$resp = file_get_contents($api);

Also, thanks for all of your time and responses, those were informational.

Answer 2

Some time we still get error with

file_get_contents($api);

in that case, try this:

fopen($api,"r");

Answer 3

You could create a stream context with the HTTP version set to 1.0 and use that context with file_get_contents:

$options = array(
    'http' => array(
        'protocol_version' => '1.0',
        'method' => 'GET'
    )
);
$context = stream_context_create($options);
$api = "http://smpp5.routesms.com:8080/bulksms/sendsms?username=$username&password=$password&source=$source&destination=$destin&dlr=$dlr&type=$type&message=$message";
$resp = file_get_contents($api, false, $context);

By the way: Don’t forget to escape your URI argument values properly with urlencode.

Answer 4

Can you sniff what's happening on the wire? Seeing the format of the HTTP request as it goes out on the wire would help a lot.

Without seeing that, my best guess would be that the server isn't well-implemented, and is rejecting a HTTP/1.1 request. Try setting --http1.0 on Curl and seeing what happens...

Answer 5

I ran into the same issue and in my case the culprit was an errant newline/CRLF character at the end of the request URL, which does not get caught by urlencode() (or maybe it does encode it but it still causes the server to produce the error). Once I found the problem the requests began to work again, even without the stream context options.

Hopefully this will help others.

Answer 6

I was also facing this same issue.. later i found that while retrieving the results from mysql, Limit $count , $count was -ve. fixing that the url worked fine. There is some problem in url only, and its not a file_get_contents or http version issue..