Hi Viggo,
the short answer is "no".
What is happening is something like this;
Browser-to-Server: Please send me "file" index.php
Server thinks: hmm php, well I know how to serve that, I load the file, pass it to my php engine, and take the result and send it back to the browser.
Server-to-browser: Here is index.php
Browser - that's not what I want, I want the "raw" file called index.php _before_ you pass it to the php engine.
Server : Sorry but I _always_ pass .php files to the php engine before serving.
--------------------
When you think about it, this is completely correct. PHP files contain "Server side code". This code contains SQL login parameters, passwords and so on. You (almost) never want random users to simply ask your server for the "raw" php.
So what to do?
Well, one option of course, is to run a NetTalk server - with PHP turned _off_ on the same machine, perhaps on a different port. It'll happily ignore the "meaning" of PHP and simply serve you the raw text if you like. (Of course this makes your _source_ code available to _anyone_ - not perhaps what you have in mind.)
An alternate is to store the index.php as index.php, but say a copy as index.raw. You can fetch index.raw without it going through the php engine (I think) unless the server is passing _everything_ to the php engine. If everything is going to the php engine then you'd need to make php.raw not-a-text-file - for example zipped.
cheers
Bruce