OK, we have an Intranet running from an IIS server (It's under Server 2k3, so that'll be IIS 6).
We have some quite weird directory structures, but everything does work.
However we've hit a problem.
At the end of a long file structre are some files that end with the extension .so
Now by default a Windows machine doesn't know what to do with a .so file.
So what I would expect to happen is you'd click on the .so file and you would get a "Please find a program to run this file" or similar.
However instead we get a 404 - File or Directory could not be found.
Odly, if we manually browse this server and using good old "Explorer" and \\servername we can browse to these .so files.
We can double-click them and indeed we get asked to provide a program to use them.
The security on the directory structure where these files are located allows full access to all - which can be shown by browsing to the location via Explorer.
It's just as if IIS doesn't know what to do with or what options to offer for therse files and throws a 404.
I've checked under "MIME types" under our IIS configuration and .so files are not listed.
I've added them - it just seems a matter of assing an extension and a free-form description.
Then a restart on IIS but still nothing.
So the basics:
Files (.so) are located in a directory within the Intranet tree that allows access to all.
Browse to the file location via a web browser and click on the file and you get a 404.
Browse to the very same directory location via Windows Explorer and you can access the files quite happily.
Is there something obvious I'm missing here?
We have some quite weird directory structures, but everything does work.
However we've hit a problem.
At the end of a long file structre are some files that end with the extension .so
Now by default a Windows machine doesn't know what to do with a .so file.
So what I would expect to happen is you'd click on the .so file and you would get a "Please find a program to run this file" or similar.
However instead we get a 404 - File or Directory could not be found.
Odly, if we manually browse this server and using good old "Explorer" and \\servername we can browse to these .so files.
We can double-click them and indeed we get asked to provide a program to use them.
The security on the directory structure where these files are located allows full access to all - which can be shown by browsing to the location via Explorer.
It's just as if IIS doesn't know what to do with or what options to offer for therse files and throws a 404.
I've checked under "MIME types" under our IIS configuration and .so files are not listed.
I've added them - it just seems a matter of assing an extension and a free-form description.
Then a restart on IIS but still nothing.
So the basics:
Files (.so) are located in a directory within the Intranet tree that allows access to all.
Browse to the file location via a web browser and click on the file and you get a 404.
Browse to the very same directory location via Windows Explorer and you can access the files quite happily.
Is there something obvious I'm missing here?
