Because the requested page type is explicitly forbidden, you cannot provide services for this type of page. The extension ". mdb" may be incorrect.

 

 

This type of page cannot be provided.

Note: The requested page type has been explicitly prohibited, so you cannot provide services for this type of page. The extension ". mdb" may be incorrect. Check the following URLs and make sure they are correctly spelled.

 

Request URL:/topskyweb/topskyadminadmin/file/temp/01sdf. MDB

 

If your program needs to download the MDB file, you only need to enable MDB download.

 

Enable download of the locked file extension

IIS protects certain file types, such as. mdb files. If the application has a locked file, perform the following operations to enable the download of such files:

 

On the "virtual directory" tab, click "Configure ".

 

You will see a list of application mappings. Delete the MDB ing of the. mdb extension to enable. MDB File Download.

 

Repeat this operation for all other extensions that you want to download as part of the application

 

The download will be successful.

 

 

 

The following describes mime knowledge:

 

1. mime and its type

1. Data Processing Methods

When the browser tries to obtain data from the server through various request methods, the server must return the correct data to the browser. The browser does not care about how the server processes it. The server can return a pre-edited HTML document and dynamically generate returned data based on the request. One of the major features of WWW is that it can be used to transmit multimedia data, and the transmission of such data is completely transparent. Through the same HTTP connection, it can transmit sound and image data in different formats. When the server is only used to return static HTML documents, the browser can easily identify their data types. However, when the server is not only used to return static HTML documents, when you can also dynamically return various types of multimedia information, the browser cannot simply judge the data that the server will return from the URL request itself.

 

 

The server and the browser use another method to identify the data type. In this way, the MIME type of the data is pre-transmitted before the real data is transmitted, to identify the data type.

 

 

2. multimedia file format MIME

In the earliest HTTP protocol, there was no additional data type information. All transmitted data was interpreted by the client program as HTML documents in the hypertext markup language. to support multimedia data types, the MIME data type information appended to the document is used in the HTTP protocol to identify the data type.

 

 

Mime is an extension of multi-purpose Internet mail. It is designed to attach multimedia data to an email so that the email client can process it based on its type. However, when it is supported by the HTTP protocol, its meaning becomes more significant. It makes HTTP transmitted not only plain text, but also rich and colorful.

 

 

Each MIME type consists of two parts. The front part is a large data type, such as audio, image, and so on. The latter part defines a specific type.

 

 

Common MIME types:

 

• Hypertext markup language text .html, .html text/html

• Plain text. TXT text/plain

• RTF text. rtf application/RTF

• GIF image. GIF image/GIF

• JPEG image .ipeg,.jpg image/JPEG

• Au audio file. Au audio/basic

• MIDI music files mid,. MIDI audio/Midi, audio/X-Midi

• RealAudio music file. Ra,. Ram audio/X-PN-RealAudio

• Mpeg file. mpg,. MPEG Video/MPEG

• AVI file. AVI Video/X-msvideo

• GZIP file. GZ application/X-Gzip

• Tar file. Tar application/X-Tar

 

 

There is a dedicated IANA organization in the Internet to confirm the standard MIME type, but the Internet is growing too fast, and many applications cannot wait for IANA to confirm that they are using the standard MIME type. Therefore, they use methods starting with X-in the category to identify this category, such as X-gzip and X-tar. In fact, these types are widely used and have become the de facto standard. As long as the client and server acknowledge this mime type together, even if it is not a standard type, the client program can process data according to the MIME type. In web servers and browsers (including operating systems), standard and common MIME types are set by default, the server and client browser must be set for identification.

 

 

Because the MIME type is related to the document suffix, the server uses the document suffix to distinguish the MIME types of different files. The server must define the correspondence between the document suffix and the MIME type. When a customer program receives data from the server, it only accepts data streams from the server and does not know the document name. Therefore, the server must use additional information to tell the customer program the MIME type of data. Before the server sends real data, it must first send the MIME type information of the Flag data. This information is defined using the Content-Type keyword. For example, for HTML documents, the server will first send the following two lines of mime identification information, which is not part of a real data file.

 

 

Content-Type: text/html

 

 

 

Note that the second act is a blank line, which is required to separate the mime information from the real data content.

 

3. For MIME types, see iana's MIME types.

 

Ii. Configure the config file

 

 

1. Enable download of the locked file extension

IIS protects certain file types, such as. config files and. mdb files. If the application has a locked file, perform the following operations to enable the download of such files:

 

• Open the "properties" page of vroot in inetmgr.

 

• On the "virtual directory" tab, click "Configure ".

 

You will see a list of application mappings. Delete the. ing of the. config extension to enable download of the. config file. Repeat this operation for all other extensions that you want to download as part of the application.

 

2. Add the config type

 

 

Mime Type ing

When published over HTTP, the MIME type of the. Application file should be "application/X-MS-application ". If. NET Framework 2.0 is installed on the server, this type is automatically set. If not, create a MIME type association for the clickonce application vroot (or the entire server.

 

Perform this operation in IIS:

 

• Run inetmgr and open the "properties" page of The vroot (or the entire server.

 

• Click the HTTP header tab.

 

• Click the file type button in the "mime ing" section.

 

• Click "New Type" to add a new type. In "related extension", type config; in "content type (MIME)", type text/XML.

 

• Restart IIS.

 

 

Iii. troubleshooting of clickonce deployment

This topic describes server prerequisites and provides a guide to common problems encountered during clickonce deployment.

 

Server Configuration

 

Enable download of the locked file extension

IIS protects certain file types, such as. config files and. mdb files. If the application has a locked file, perform the following operations to enable the download of such files:

 

• Open the "properties" page of vroot in inetmgr.

 

• On the "virtual directory" tab, click "Configure ".

 

You will see a list of application mappings. Delete the. ing of the. config extension to enable download of the. config file. Repeat this operation for all other extensions that you want to download as part of the application.

 

For security reasons, some Web server configurations block files that are not often used for web content. For example, files with the following extensions may be blocked:. dll,. config,. MDF. Windows-based applications usually contain files with some extensions. If the clickonce application you are trying to run needs to access the blocked files on the web server, an error occurs. You do not need to block all file extensions. By default, each application file is published with the ". Deploy" file extension. If you use this option, you only need to configure the following three file extensions for the Web Server:

 

•. Application

 

•. Manifest

 

•. Deploy

 

However, you can disable this option by clearing the "use 'ploy' file extension" option in the "Publish options" dialog box, in this case, you must configure the Web server to allow all file extensions used in the application.

 

Sometimes you must configure. manifest ,. application and. deploy, for example, not installed in use.. NET Framework, or other Web servers (such as APACHE.

 

Configure expiration settings

When an application is started through a URL, Internet Explorer Downloads the. Application file. Therefore, the expiration settings for all cached files in the browser will be valid. The client uses. Application in the IE cache instead of detecting new updates. To ensure that the client detects updates whenever updates are available, enable the "expire now" option in IIS.

 

Perform this operation in IIS:

 

• Run inetmgr and open the "properties" page of The vroot (or the entire server.

 

• Click the HTTP header tab.

 

• Click Enable content expiration ".

 

• Click "expire now ".

 

• Restart IIS.

 

FTP protocol not supported

Clickonce supports installation of applications from any HTTP 1.1 web server or file server. The FTP protocol is not supported. You can use ftp: // protocol to publish an application, but you must use http: //, https: //, or file: // protocol for installation.

 

Correctly Configure the server

One of the most common problems when using clickonce is that clickonce cannot download files from the network server due to configuration problems. If you encounter a File Download problem during clickonce installation, try to download the same file using Internet Explorer. In this way, the problem scope will be reduced to the clickonce problem, rather than the common server/network problems.

 

Administrator privilege required

If HTTP publishing is used, you must have the administrator privilege on the target server (this privilege level is required for IIS ). If HTTP publishing is not used, you only need to have the write permission on the target path.

 

Anonymous access must be enabled

When you publish a message to a remote server with "Anonymous Access" disabled, you will receive the following warning:

 

"The files cocould not be downloaded from http: // <remoteserver>/<myapplication> /. the remote server returned an error: (401) Unathorized. "To solve this problem, right-click my computer in Windows Resource Manager and select" manage ". In the "Computer Management" dialog box, open the "service and application" node, "Internet Information Service", and "website", and right-click "default website ". In the "default website properties" dialog box, click the "Directory Security" tab, and then click the "edit" button. In the "authentication method" dialog box, select the "Anonymous Access" check box.

 

Windows XP SP2: Windows Firewall

By default, Windows XP SP2 enables Windows Firewall. If applications are developed on a computer installed with Windows XP, clickonce applications can still be published and run from the local IIS server. However, if Windows Firewall is not enabled, the IIS server cannot be accessed from other computers. To manage Windows Firewall, select Windows Firewall from control panel ".

 

Windows Server 2003: Enable FrontPage Server Extension

To publish an application to a Windows Web server over HTTP requires the FrontPage Server Extension (FPSE ).

 

By default, FPSE is not installed on Windows Server 2003. If you want to use Visual Studio to publish an application to the Windows Server 2003 Web server through HTTP with FPSE, you must first install FPSE. You can use the "manage your servers" management tool in Windows Server 2003.

 

Mime Type ing

When published over HTTP, the MIME type of the. Application file should be "application/X-MS-application ". If. NET Framework 2.0 is installed on the server, this type is automatically set. If not, create a MIME type association for the clickonce application vroot (or the entire server.

 

Perform this operation in IIS:

 

• Run inetmgr and open the "properties" page of The vroot (or the entire server.

 

• Click the HTTP header tab.

 

• Click the file type button in the "mime ing" section.

 

• Click "New Type" to add a new type. In "related extension", type application; in "content type (MIME)", type application/X-MS-application.

 

• Restart IIS.

 

Windows Server 2003: Locked MIME type

IIS on Windows Server 2003 locks all file types except some known types (such as .htm).html#.txt. To use this server to deploy a clickonce application, you need to change the IIS settings to allow downloading. Application,. manifest, and all other custom file types used by the application.

 

Perform this operation in IIS:

 

• Run inetmgr and open the "properties" page of the Computer node.

 

• Click the MIME type button.

 

• Click the new button and add the new extension and necessary MIME types.

 

For. Application and. manifest extensions, the MIME type should be "application/X-MS-application ". For other file types, the MIME type should be "application/octet-stream ".

 

If you create a MIME type with the extension "*" and the MIME type is "application/octet-stream", files of the unblocked file type can be downloaded. (But cannot download blocked file types, such as. aspx and. asmx ).

 

• Restart IIS.

 

 

 

 

 

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/Bobwu/archive/2010/04/14/5483609.aspx