ForceType Problem

forcetype to php causes "save" dialogue to appear

[geckofuel]

When using the following in an .htaccess file to cause "filename" to be parsed as PHP,

<Files filename>
ForceType application/x-httpd-php
</Files>

I get a "Save As" dialogue in both IE 6 and Netscape 7 when I try to access the URL "http://myserver.com/filename". Any ideas on what the problem could be?

[vincevincevince]

check the content type headers you're putting out
use a server header checker for that

[geckofuel]

vince,
I followed your advice, and went here:
[searchengineworld.com...]

However, I'm not sure what to be looking for. Could you give me a few tips?

[geckofuel]

This might be relevant, but I need help interpreting it:

Status: HTTP/1.1 200 OK
Date: Sun, 13 Jul 2003 12:16:21 GMT
Server: Apache/1.3.26 (Unix) FrontPage/5.0.2.2623
Last-Modified: Sat, 12 Jul 2003 02:27:50 GMT
ETag: "9269a2-2ee9-3f0f7226"
Accept-Ranges: bytes
Content-Length: 12009
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html

[vincevincevince]

Those headers look okay ... can you sticky me your URL and I'll have a poke around?

[geckofuel]

That is another interesting problem that I am having.

[myserver.com...] is handled differently than [myserver.com...] where the former seems to be getting the ForceType applied (though something wrong is happening), while the latter is being seen as a nonexistent file/folder.

[geckofuel]

Could this be a problem? The httpd.conf file has the following line:

TypesConfig conf/mime.types

However, the conf folder does not contain a file called mime.types.

Is this a problem, and if so, is there a standard "mime.types" file that I could place in the conf folder?

[olwen]

What version of Apache? I found I had to use
acceptpathinfo on
as well in my test environment with Apache 2