Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies. Mysql_fetch_array — Recupera una fila de resultados como un array asociativo. Como generar archivos excel desde php correctamente. Si quier usar esto para guardar el archivo en el servidor, en vez de descargarlo desde el. Hp Fan Speed Control Software.

I couldn't for the life of me get a certain php script working when i moved my server to a new Fedora 4 installation. The problem was that fopen() was failing when trying to access a file as a URL through apache -- even though it worked fine when run from the shell and even though the file was readily readable from any browser.

Hp M7470n Driver File System Srvnet. After trying to place blame on Apache, RedHat, and even my cat and dog, I finally ran across this bug report on Redhat's website: Basically the problem was SELinux (which I knew nothing about) -- you have to run the following command in order for SELinux to allow php to open a web file: /usr/sbin/setsebool httpd_can_network_connect=1 To make the change permanent, run it with the -P option: /usr/sbin/setsebool -P httpd_can_network_connect=1 Hope this helps others out -- it sure took me a long time to track down the problem. PHP will open a directory if a path with no file name is supplied. This just bit me. I was not checking the filename part of a concatenated string. For example: Will open the directory if $somefile = ' If you attempt to read using the file handle you will get the binary directory contents. I tried append mode and it errors out so does not seem to be dangerous.

This is with FreeBSD 4.5 and PHP 4.3.1. Behaves the same on 4.1.1 and PHP 4.1.2.

I have not tested other version/os combinations. This is an addendum to ibetyouare at home dot com's note about Apache directory permissions. If you are on a shared host and cannot tweak Apache's permissions directives then you might try setting the same thing in a.htaccess file. Failing that, if you are having trouble just creating files then set the directory permissions to allow writing (for whatever directory the file is supposed to be in) and include the following before fopen(): `touch /path/to/myfile/myfile.txt`; That will usually create a new empty file that you can write to even when fopen fails. TIP: If you are using fopen and fread to read HTTP or FTP or Remote Files, and experiencing some performance issues such as stalling, slowing down and otherwise, then it's time you learned a thing called cURL.

Performance Comparison: 10 per minute for fopen/fread for 100 HTTP files 2000 per minute for cURL for 2000 HTTP files cURL should be used for opening HTTP and FTP files, it is EXTREMELY reliable, even when it comes to performance. I noticed when using too many scripts at the same time to download the data from the site I was harvesting from, fopen and fread would go into deadlock.

When using cURL i can open 50 windows, running 10 URL's from each window, and getting the best performance possible. Just a Tip:).

To overwrite a file with a new content without deleting it, and without changing the owner or access rights, it's best to not use: but instead the faster one: The reason is that truncating a file at size 0 forces the OS to deallocate all storage clusters used by the file, before you write your content which will be reallocated on disk. Rest Download File Php Example Function. The second code simply overwrites the existing content where it is already located on disk, and truncates any remaining bytes that may exist (if the new content is shorter than the old content). The 'r+b' mode allows access for both read and write: the file can be kept opened after reading it and before rewriting the modified content. It' s particularly useful for files that are accessed often or have a size larger than a few kilobytes, as it saves lots of system I / O, and also limits the filesystem fragmentation if the updated file is quite large.

And this method also works if the file is locked exclusively once opened ( but I would rather recommend using another empty file for locking purpose, opened with 'a+' access mode, in '/var/lock/yourapp/*' or other fast filesystems where filelocks are easily monitored and where the webserver running PHP is allowed to create and update lock files, and not forgetting to close the lock file after closing the content file ). The verbal descriptions take a while to read through to get a feel for the expected results for fopen modes. If you're running PHP as apache module, it will always write files as 'nobody', 'www', 'httpd', (or whatever user your webserver runs as) unless you specify a different user/group in httpd.conf, or compile apache with suexec support. However, if you run PHP as a CGI wrapper, you may setuid the PHP executable to whatever user you wish (*severe* security issues apply). If you really want to be able to su to other user, I recommend compiling with suexec support. AFAIK, PHP can't NOT use SuEXEC if apache does. If PHP is configured as an apache module it will act as whatever user the apache is.