Phil,
Thanks for the response to this. I have a similar problem to discuss with you. I've recently been forced to turn off the mime magic module, because it was taking taf files that had <html> or <head> in the response action cdata and not sending it to the witango server. I commented out all the lines in the magic file that looked for text/html files but magic was still causing some files to be served up without app server processing (yes i restarted the server)
So i decided to just turn off the mime magic module entirely, and now those pesky tafs are running fine. (still can't figure out why mime magic was causing it to not work)
So here are my questions.
Is the use of the ForceType directive going to take precedence over what mime-magic tries to do? If so, does it hurt to add them for .taf .tcf and .tml as well so that i don't have to worry about magic screwing up.
Also, without any ForceType directives in the configuration files, and a fresh Witango install, what causes the standard extensions to get processed by the witango app server? Does the module have "Directives" hard coded into it? ( you'll have to forgive me as I don't know anything about how a module like the witango one works on apache.)
Thanks, John
Phil Wade wrote:
Here is how it is really done with Apache 2 ...
You need to change the mime type of the request so that the witango plugin will pick it up and process it.
<Directory /> Options FollowSymLinks AllowOverride None
<Files *.html> ForceType application/witango-application-file </Files> </Directory>
This will force all html files in the / directory to have a mime type that will be processed by the witango plugin for apache 2.
You can set this directive based on virtual hosts or globally.
Regards
Phil
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
