Justin,
Mixed linux/unix/OS X and windows is not a configuration we have on
our test matrix as up until recently the companies were normally
polarised regarding the OS for serves.
A simple test would be to create a helloworld.html file. See if
apache servers it. Then change the .html of the file to .tml and see
if the Witango server will process it. This should resolve whether
permissions are part of your problem.
It may be an issue with / vs \ for the different file systems. IIS
may be doing some conversion of / from the URL to \ for the file
system which apache2 on Linux doesn't do because it is expecting to
be talking to a linux file system.
What are your apache logs and witango logs showing in terms of the
file each process is looking for? Are the / the right way around
for the respective OS.
If you run up something like tcpflow, you can see what is being sent
between the witango apache 2 module on linux to the Witango server on
Windows? The LISTENERPORT in the witango.ini file will tell you what
port to filter on. You should be able to see if apache has found the
file and sent it to the Witango server and what path is sent to the
Witango Server. If you have file caching turned on try turning it
off and see if it makes a difference.
Regards
Phil
On 21/07/2006, at 7:18 AM, Justin Smith wrote:
Hello all,
My company currently runs two Witango Server 5.5 application
servers (on Windows 2000), and one web server running IIS (also on
Windows 2000). I am now trying to configure a new SuSE Linux/
Apache2 web server to talk to the existing Witango app servers. I
was able to get the Witango plugin for Apache2 installed, and it is
currently talking to the Witango servers, but I am running into a
problem. Every time I attempt to access a TAF file, I get the
"application file was either missing or invalid" error message
(error number -3).
I know that it is hitting the Witango servers, because it is
displaying our custom error page. The path to the TAF files is the
same on the Apache2 server as it is on the IIS servers (relative to
the web root), and Apache serves HTML files in the same directories
without a problem.
File caching was enabled on the Witango servers, but the same
problem occurs when caching is disabled.
It did not appear to be a problem with DOS vs. Unix newlines, as I
have tried converting the files to no avail.
I have the mod_speling module loaded, so it does not appear to be a
problem with URL case.
I'm running out of ideas here... Has anyone run into this problem
before?
Thanks in advance for any help you can provide.
--
Justin Smith.
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
