The online FAQ database contains hundreds of answers to frequently asked questions, articles on using our
web server applications and other related technologies, and resolutions to common problems. If you are seeing
an error message, be sure to try searching on the error message or error number that you are seeing.
|
| |
| |
| |
| |
|
Why do I need a component to upload images (files) to my web server through the browser?
|
|
|
Modern browsers can allow the end user to upload files to a web server from right within the browser itself. This capability has two requirements in order for it to work. First, on the end user's browser, the browser must be able to read the file and encode it for transmission to the webserver in a standard way (this is known as being RFC 1867 compliant). Second, the web server must be able to efficiently decode that information and save it on the webserver. Current releases of Internet Explorer, Netscape Navigator, Mozilla and most other recent browsers can do browser based uploads (pre 4.x generation browsers of IE or Navigator usually cannot).
IIS/ASP does not provide any built-in direct support for decoding the file upload to the web server through ASP. Trying to decode the file with ASP script alone would be a slow and inefficient process, especially with large files. This is why a component is required.
All current XCENT web server applications that have upload functionality can support the following upload components:
Most of our applications also support these components:
Please note that the upload component needs to be installed on the web server itself; therefore, if your site is being hosted by an ISP, this is something you would have to ask your host if they provide. Most ISP's already offer at least one of our supported upload components.
|
|
|
|
| |
