IE7 prompts for open/save of .asp files

[os400]

I have a weird issue where asp pages are not auto loaded in my IE7 browser. I'm prompted with a File Download dialog box with the following:

Some files can harm your computer. If the information below looks suspicious do not open or save this file:

File Name: doctl.asp

So far, I've looked at the file associations stuff thru explorer and checked/unchecked 'confirm open after download' in the advanced settings. Everything else I've seen has been directed at the developer side of things.

TIA

Mike Butler
Now former Iseries Guy -> PC's back, SUNs gone Iseries gone- BooHoo
"Never put off 'til tomorrow what you should have done yesterday

 

[smah]

Try resetting the security settings back to default for whichever zone you are in when this occurs (probably internet zone). Tools, Internet Options, internet (or whatever) zone, Custom Level button, Reset button.

 

[blueark]

Could be a problem with the server too. Does it happen with all ASP pages (e.g. try

http://www.w3schools.com/xml/default.asp),

or just on one particular site? If you go ahead and download the asp file, then open it in NotePad, can you see any asp scripting? (it's usually delimited by <% %>)

If that's the case, it's a problem at the server end rather than your browser. There are many server-side technologies (.asp, .aspx, .php, .jsp, etc), and the server has to be set up to process the ones being used, and output something the browser can use (usually HTML). For whatever reason, asp pages are not being processed, so they're effectively just ordinary files.

 

[os400]

this problem is confined to just one system.

Mike Butler
Now former Iseries Guy -> PC's back, SUNs gone Iseries gone- BooHoo
"Never put off 'til tomorrow what you should have done yesterday

 

[blueark]

To clarify: "Confined to one system" as in:

1: All the asp pages are on the same PC

or

2: One browser on your PC is downloading asp pages as files, regardless of where they are located (including the W3schools link in the last post)


If it's (1), start with the basics. Are the asp pages on your own local PC, or on a remote host? If local, does the address in your browser start with 'file://' (which means they won't be interpretted properly) or 'http:localhost....' (in which case, you might need to look at your IIS settings)? If remote, does your hosting provider support ASP, and if so, is it active? They probably have a control panel or similar to check this with.