Although it is common, using *.inc to name your asp includes is not a good idea. Say you have an include in a folder, like /www/includes/login.inc. Now suppose I figure out where this include lives on your webserver. If I can gain access to the *.inc file, then I can read all of your asp code. If the include is named *.asp, then it will be executed before it is sent to the client and thus I won't be able to read your code. So name anything with asp code in it as *.asp.
If your code isn't being executed before it is being sent out to the client then there is either something wrong with your server configuration or (sometimes) your code. It has nothing to do with the client browser.
well, it isn't even on a server (yet)...so i am not expecting it to do anything, but when i "preview" the page (that contains asp) in say safari, i get a page as it looks...but in firefox when i preview it, i get the asp code as text on the page.
Unless you're accessing the file differently in the two browsers (ie. "C:/dir/dir/file.asp" vs. "http://localhost/file.asp") then the source should be the same. View the source in each browser and they should be identical. It doesn't make sense that they wouldn't be. Safari and firefox may parse the asp code tags differently (I'm not sure), but the source code will be the same.
what jfulton was saying about using ASP.
even if you do not have ASP code in it, it is a good idea just to force the habit
but for instance, I know a lot of people that set up their data access (connection strings) as a separate file and include it into their pages so they do not have to code it over and over...
if it is INC... and I figure it out... I then can get complete access to your database, possibly even your hosting account if your username and password are the same.
Providing Technology services to non profit orgs, Homeless Shelters, Food Pantries, Clean And Sober Houses and more. To date we have given away over 900 free computers !
caeli enarrant gloriam Dei !