Printable View
I am coding a webserver, and I would like to be able to detect what kind of file I am sending to the client, but I do not know of a good function for this, so if anyone could point me towards one, I would be very grateful.
By file type I mean files such as JPG, PNG, HTML etc, so I can include the correct data in the header.
I am coding pure C in a Unix environment.
I assume the "obvious" (and error prone) method of looking at the extension has been examined and rejected?
If you're on Unix, you have a "file" command. If it's a free Unix (and perhaps commercial ones), your "file" program is likely based on libmagic, which can determine file types quite accurately. Try "man libmagic". If you don't have it, you can download it from ftp://ftp.astron.com/pub/file/.
files is only accessible from the shell, is it not?
either way, it wont work, since my computer is in some way defect and freezes indefinately when you use the make command, so manually installing new software is impossible.
telling me to reformat is of no use since the problem lies with the hardware, but the producer (HP) have still failed to locate the problem after over 2 years, and instead are recalling this model, and I have broken the seal so I can not return mine *yay*.
file is not only accessible from the shell, but I suggested using libmagic, not file.
That doesn't solve your make problem, but if you have libmagic (not just file) installed, you can use libmagic; you don't need to run the file program.
Ehm, if they are recalling the product, I would say that you should have the right to get a replacement/refund even if the seal is broken - why should instaling an extra hard-drive cause the recall to be invalid - it's not you installing the extra harddrive that caused the problems, right? [Installing an extra hard-drive is of course just an example, replacing the graphics card, extra network card, or whatever it is].Quote:
Originally Posted by Siphon
I would have a chat with a HP support Supervisor about this case and make sure you explain to them that you do think it's unfair that just because you installed a second hard-drive [or whatever the reason you broke the seal is - don't say "I thought I could fix it by opening the box" of course - even if that was the reason] before you actually put the machine into it's real work, and you didn't expect it to have to be returned for a manufacturing flaw.
--
Mats