PHP ini file get contents external url

Question

I use following PHP function   file get contents  http   example com     Whenever I do this on a certain server  the result is empty  When I do it anywhere else  the result is whatever the page s content may be  When I however  on the server where the result is empty  use the function locally - without accessing an external URL  file get contents     simple internal path html      it does work   Now  I am pretty sure it has something to do with a certain php ini configuration  What I am however not sure about is  which one  Please help

User · Answer

Enable allow url fopen From cPanel Or WHM in PHP INI Section

User · Answer

ch   curl init    curl setopt  ch  CURLOPT URL   http   www your external website com    curl setopt  ch  CURLOPT HEADER  0   curl setopt  ch  CURLOPT RETURNTRANSFER  TRUE    result   curl exec  ch   curl close  ch     is best for http url  But how to open https url help me

User · Answer

This will also give external links an absolute path without having to use php ini   lt  php  ch   curl init    curl setopt  ch  CURLOPT URL   http   www your external website com    curl setopt  ch  CURLOPT HEADER  0   curl setopt  ch  CURLOPT RETURNTRANSFER  TRUE    result   curl exec  ch   curl close  ch    result   preg replace     lt  s a s    gt   href s   s          http        gt          gt         1http   www your external website com  2 3    result   echo  result   gt

User · Answer

Add   allow url fopen 1   in your php ini file  If you are using shared hosting  create one first

User · Answer

The setting you are looking for is allow url fopen   You have two ways of getting around it without changing php ini  one of them is to use fsockopen    and the other is to use cURL   I recommend using cURL over file get contents   anyways  since it was built for this

User · Answer

Complementing Aillyn s answer  you could use a function like the one below to mimic the behavior of file get contents   function get content  URL          ch   curl init          curl setopt  ch  CURLOPT RETURNTRANSFER  1         curl setopt  ch  CURLOPT URL   URL          data   curl exec  ch         curl close  ch         return  data     echo get content  http   example com

User · Answer

The answers provided above solve the problem but don t explain the strange behaviour the OP described  This explanation should help anyone testing communication between sites in a development environment where these sites all reside on the same host  and the same virtualhost  I m working with apache 2 4 and php7 0    There s a subtlety with file get contents   I came across that is absolutely relevant here but unaddressed  probably because it s either barely documented or not documented from what I can tell or is documented in an obscure php security model whitepaper I can t find    With allow url fopen set to Off in all relevant contexts  e g   etc php 7 0 apache2 php ini   etc php 7 0 fpm php ini  etc     and allow url fopen set to On in the command line context  i e   etc php 7 0 cli php ini   calls to file get contents   for a local resource will be allowed and no warning will be logged such as   file get contents  php   input      or     Path outside document root that webserver user agent has permission to read  e g  for an apache2 webserver this user agent might be www-data so a file at  etc php 7 0 filetoaccess would be successfully read if www-data had permission to read this file file get contents   lt file path to file on local machine user agent can access gt       or     Relative path in same document root file get contents  data filename dat     To conclude  the restriction allow url fopen   Off is analogous to an iptables rule in the OUTPUT chain  where the restriction is only applied when an attempt to  exit the system  or  change contexts  is made   N B  allow url fopen set to On in the command line context  i e   etc php 7 0 cli php ini  is what I had on my system but I suspect it would have no bearing on the explanation I provided even if it were set to Off unless of course you re testing by running your scripts from the command line itself  I did not test the behaviour with allow url fopen set to Off in the command line context

User · Answer

The is related to the ini configuration setting allow url fopen   You should be aware that enable that option may make some bugs in your code exploitable   For instance  this failure to validate input may turn into a full-fledged remote code execution vulnerability   copy   GET  file

[php] PHP ini file_get_contents external url

Examples related to php

Examples related to url

Examples related to external

Examples related to file-get-contents

Examples related to ini