unlink not deleting file

[andy98]

Hi

I am trying to remove an image file from a webserver and have got 777 permissions on the directory but cannot remove the file.

I know the action part is working and it is entering the IF statement! And I know that the $filename returned can be accessed when I paste it into a web browser.

Is my code incorrect?

$filename = "[URL unfurl="true"]http://www.mywebsite/images/$_GET[/URL][fullpic]";

if ($action == 'delImage')
{

echo "$filename<br><bR>";

		if(file_exists($filename))
		{
		echo "File does exist really";
		unlink($filename);
		}

		else
		{
		echo "the file does not exist";
		} 
}

And even when I place my UNLINK somewhere in the IF statement where is does get processed all I get back is:

Warning: Unlink failed (No such file or directory)

http://www.goplanetgo.co.uk

 

[Olavxxx]

I think that you should do:
if (is_file("images/$_GET[fullpic]") {
}

Olav Alexander Mjelde

http://www.volvo-power.net

Admin & Webmaster

 

[andy98]

Hi

I just solved the problem!

$filename = "

http://www.mywebsite/images/$_GET

[fullpic]";

is incorrect!

You have to use:

$filename ="/home/mywebsite/images/$_GET[fullpic]";

Thanks anyway

http://www.goplanetgo.co.uk

 

[DRJ478]

Sometimes the URL wrappers provided with PHP come back to bite you. It seems to cloud peoples' understanding about the differences between files conveniently retrieved via HTTP requests and directly read from the file system.
It would be absolutely horrible if files could be deleted via HTTP requests.

 

[ingresman]

you can, this is from the HTTP rfc.

9.7 DELETE
The DELETE method requests that the origin server delete the resource identified by the Request-URI. This method MAY be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation has been carried out, even if the status code returned from the origin server indicates that the action has been completed successfully. However, the server SHOULD NOT indicate success unless, at the time the response is given, it intends to delete the resource or move it to an inaccessible location.

A successful response SHOULD be 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has not yet been enacted, or 204 (No Content) if the action has been enacted but the response does not include an entity.

If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries SHOULD be treated as stale. Responses to this method are not cacheable.

 

[748323]

Seems like you overdoing it. More is not always better.