ForceType directive and Apache config

Hello,

I have two experimental accounts that I use to play with different web stuff
on a cheapie shared hosting service, two different domains.

I'm guessing that the two domains are on two different servers because one
server supports the htaccess ForceType directive, and the other generates a
500 error (Internal Server error) when I try to access the ForceType
directive target file as a URL. The test files and directory structure are
identical between the two accounts.

What is the difference between Apache configurations that allows the
ForceType function to work on one config and not another?

Is this something I can fix on my end, or does a sys admin need to get
involved (is there a workaround)?

Also, why do some Apache configs need "application/x-httpd-php" as the
ForceType file type, and others have to have just "x-httpd-php"?

Thanks,

--
Robert

Robert Oschler <no_replies DeleteThis @fake_email_address.invalid> wrote:
 > What is the difference between Apache configurations that allows the
 > ForceType function to work on one config and not another?

OptionOverride ForceType

 > Is this something I can fix on my end, or does a sys admin need to get
 > involved (is there a workaround)?

Yes, he does need to be involved. Besides, if one allow this and the
other doesn't, maybe is just a mistype on their ends. Drop him a mail.

Davide

--
| All true wisdom is found on T-shirts.
|
|
|<!-- ~MESSAGE_AFTER~ -->