Aliases used for the internal or an external server


Probably you will want to have your entire web site off-line, with all it's subfolders, exactly as on your remote host, so that developing will be easier. However if all the html documents and scripts are not under a single folder, you will need to use aliases, to correspond URL addresses and absolute paths to the files.


For example if you have your files under c:\webs\myweb, and your cgi-bin folder is under c:\webs\myweb\cgi-bin then aliases are not needed. Setting a webroot of c:\webs\myweb will map correctly all URL requests to the files, bu the path in the URL address. http://localhost/index.html and http://localhost/cgi-bin/test.cgi will view files c:\webs\myweb\index.html and c:\webs\myweb\cgi-bin\test.cgi.


But if your server cofiguration has a cgi-bin folder outside of the path were you have html documents (like apache servers) or you have other mappings of url addresses to real paths, then you need aliases. For example, if you have folders:


c:\webs\myweb\htdocs that hold all your html files and

c:\webs\myweb\cgi-bin for scripts, then you will need to setup an alias:




This way accessing http://localhost/cgi-bin/ will get c:\webs\myweb\cgi-bin and not the incorrect c:\webs\myweb\htdocs\cgi-bin (presumming you have set up c:\webs\myweb\htdocs as document root).


If you use the internal server, enter this in the "aliases" field of the internal server. If you use an external server, enter in aliases for the external server.


icon_idea See common scenarios for some common set-ups.


icon_idea If you use Apache, the aliases in it's httpd.conf file can be parser automatically by pressing the "parse" button in the options or project options.


Aliases in the Remote transfer session window


Aliases in the "Running remote files" section of the transfer session setup are like the above, but work the other way around. Optiperl knows the remote path of the file, from when you downloaded it. If you try to run, optiperl will guess the url that needs to be sent to access it. Again all your files are under a single folder, aliases are not needed. Here are some examples:


Document Root: /htdocs/

Links to:

Aliases: /cgi-bin/=; /perl/=;


With the above, a remote file opened from /htdocs/ will be run as and a file from /cgi-bin/ will be run as


icon_idea See common scenarios for some common set-ups.



Top  Previous  Next