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

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 it? The portion of the code is:

$api = "$username&password=$password&source=$source&destination=$destin&dlr=$dlr&type=$type&message=$message";
$resp = file_get_contents($api);

The server responded correctly while I pasted the url in the browser.
I learned that this is caused by the server rejecting the client’s HTTP version, but I have no idea why that is happening in my case.

Any help is much appreciated. Thanks in advance

Here is Solutions:

We have many solutions to this problem, But we recommend you to use the first solution because it is tested & true solution that will 100% work for you.

Solution 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 = "$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.

Solution 2

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 = "$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.

Solution 3

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.

Solution 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…

Solution 5

Some time we still get error with


in that case, try this:


Solution 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..

Note: Use and implement solution 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply