Project

General

Profile

Actions
Copy link

Bug #831

closed

Content-Type is always text/html when using X-LIGHTTPD-send-file from PHP fastcgi

Added by Anonymous over 18 years ago. Updated over 17 years ago.

Status:
Fixed
Priority:
Normal
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:

Description

I'm trying to protect some video files behind a PHP script, because I need to rename them on the fly, otherwise I'd stick with mod_secdownload. My problem is that although I don't set any Content-Type header from PHP, it always ends up being "text/html" instead of the correct type which is configured in lighttpd.

It seems like lighttpd should be able to properly set that header since I see that it properly sets the Content-Length header already.

I also noticed that I could force the Content-Type to something else from the PHP script, so maybe it's PHP defaulting to text/html and lighttpd not wanting to overwrite it? Still, I'm not sure which behavior makes more sense... either way, some mean to force the Content-Type of a file sent by X-LIGHTTPD-send-file to be the mime type configured in lighttpd would seem to make sense to me.

-- matthias

Actions
Copy link
 #1

Updated by jan over 18 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

X-Sendfile is only changing the Content of the response and none of the headers. As PHP uses Content-Type: text/html by default your content will be announced as HTML. lighttpd is only forwarding the headers and replaces the content.

Closed with: not a bug.

Actions
Copy link
 #2

Updated by rhinofly about 18 years ago

I have post a short script for send custom Content-Type base on the file name in the topic:

http://forum.lighttpd.net/topic/4403#5910

Hope this help more people.

Actions
Copy link
 #3

Updated by Anonymous about 18 years ago

  • Status changed from Fixed to Need Feedback
  • Resolution deleted (invalid)

Hi, I had long since forgotten this bug :-) Anyway, I know how to override the Content-Type from the PHP script, it's just that it would make more sense to me to have lighttpd be able to generate the header itself, based on the extension of the file passed to X-LIGHTTPD-send-file.

For now, what I've done in PHP is to use the fileinfo PECL module :


// Get file MIME type
if (function_exists('finfo_open')) {
        $finfo = finfo_open(FILEINFO_MIME, "/usr/share/magic");
        $mimetype = finfo_file($finfo, $file);
        finfo_close($finfo);
} else {
        $mimetype = "application/force-download";
}
header("Content-Type: " . $mimetype);

But this is all redundant, and will only slow things down. How hard would it be to have a lighttpd configure option like "x-send-file-mime-override" => <boolean> which would send out the mime type configured in "mimetype.assign" for the file extension being sent by X-LIGHTTPD-send-file?

Jan : About your first comment, lighttpd seems to be changing at least one header when X-LIGHTTPD-send-file is used, the Content-Length one.

-- matthias

Actions
Copy link
 #4

Updated by jan over 17 years ago

  • Status changed from Need Feedback to Fixed
  • Resolution set to fixed

One line in PHP vs. several lines of code in lighttpd + config-options.

Nope, I don't see a benefit in such a feature for now. Anyway, please open a feature request instead of reopening this bug. :)

Actions
Copy link

Also available in: Atom