archive-de.com » DE » H » HAB.DE

Total: 20

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Administration
    in the default xitami aut file to indicate that the administration URL admin is not accessibly until a non default password has been entered An empty password is treated as meaning non required for that user The entry all allows access to all users without a user id password check You can combine this with the webmask option to restrict access by webmask without requiring user id password entry at the same time Xitami Log Files The Xitami Server Log File Xitami logs errors and information to the file xitami log This file is always opened in append mode It looks something like this 96 12 05 20 19 41 I OPEN port 80 96 12 06 07 22 03 I OPEN port 80 To configure the server log see the Serverlog configuration entry By default Xitami logs all HTTP requests to the file access log which follows the common CERN NCSA standard for web server log files The log file format consists of lines in this format host user DD Mon YYYY hh mm ss request ddd bbbb referer agent This field Has this purpose host IP number of requesting host user Userid sent for authentication or request HTTP request sent by client ddd Status code returned by server bbbb Size of data sent excluding HTTP header referer Referer document or agent User agent browser or The access log files are automatically cycled when Xitami starts it will save any existing file before starting a new access log The old access log file is given a name based on the date when it was last modified Extended Logging Xitami has an extended logging function that is much richer than the standard access logging function The extended logging function gives you more control over the way that log files are cycled over the log file names and over the log file format The extended logging function also does reverse DNS translation of IP addresses The extended logging function works with access logs and error logs and is controlled by a number of additional configuration options in the ServerLog AccessLog ErrorLog FTPLog and FTPErrLog sections format Specifies the log file format You can use one of a number of predefined formats or build your own format using any of these symbols Symbol Expands to give client client address as translated string ipcli client address as dotted number ipsrv server address as dotted number request request line HTTP only query query string if any HTTP only method HTTP method or FTP command status response code 3 digits recd request size in bytes sent response size in bytes time ms request duration in msecs time s request duration in seconds n nnn file filename to which request was translated agent HTTP user agent browser name referer HTTP referer field user user name if any else service name of service HTTP FTP vhost virtual host name if any else datetime date time in NCSA format yy year as two digits year year as four

    Original URL path: http://allegro.hab.de/xitami/index3.htm (2016-02-14)
    Open archived version from archive

  • Configuration
    if wanted the cost of an open connection is low and does not degrade the server performance Anything more than a minute or so is probably not worth it Default 30 seconds default n Specifies the default files Up to 32 default files can be specified When the user specifies a URL without filename the server searches the directory for the default files in order from default1 to default32 until a matching file is found or the default sequence ends Note that Xitami automatically looks for html extensions if a htm file is not found Default default1 index htm default2 default htm cache defaults Normally defaults pages are cached like any other This means that if the browser has already loaded the page it will add a HTTP request header If Modified Since Xitami uses this date to determine whether to send the page or not In most cases it is appropriate to leave this option enabled However if you are developing several sites you may find that the browser shows the default page from one site when you look at another You can clear the browser cache and reload but this is usually pretty tiresome So disable this option and Xitami will never cache defaults pages error header Specifies the text used to preface an HTTP error message The text may either be HTML or a filename prefaced by If the text comes from a file Xitami will re read this file each time it sends an error response Default HTML TITLE Error TITLE BODY H1 B error footer Specifies the text used to end an HTTP error message The text may either be HTML or a filename prefaced by If the text comes from a file Xitami will re read this file each time it sends an error response Default B H1 BODY HTML text xxx Specifies the text used for a specific HTTP error code The text may either be HTML or a filename prefaced by If the text comes from a file Xitami will re read this file each time it sends an error response The text is always prefixed by the error header and suffixed by the error footer You can use this for error codes 4xx and 5xx 2xx codes are not errors and 3xx codes are handled by the browser without displaying any text that the server might send To test a specific error you can use the special URL error xxx For instance to simulate a 402 error Payment Required use a URL like this http 127 0 0 1 error 402 You can simulate a 302 error temporary redirection using a URL like this http 127 0 0 1 error 302 somedir somepage htm The error codes returned by Xitami are 200 Ok 201 Created 202 Accepted 203 Partial information 204 No response 301 Moved 302 Found 303 Method 304 Not modified 400 Bad request 401 Unauthorized 402 Payment required 403 Forbidden 404 Not found 412 Precondition failed 413 Request entity too large 500 Internal error 501 Not implemented 502 Service temporarily overloaded Default HTTP 1 0 XXX error text priority Specifies the server priority on systems where this is possible currently only Windows NT and 95 1 normal 2 low 3 high You can set the priority to low for systems where the server should not interfere with other processes You can set the priority to high for systems where the server is the main process ipaddress Specifies the IP address on which Xitami should open its HTTP connection If this is 0 Xitami will open its connection on all available IP addresses This is normally a Good Idea since it makes configuration much simpler on a multihomed system and is completely correct on a single homed system i e a system with just one IP address which is pretty common If you have multiple IP addresses and want to run Xitami on just one of these you can specify it here using the standard dotted network address format This will effectively disable IP based virtual hosting Default 0 take any available IP address portbase Defines the IP port base for the server Add 80 to this to calculate the actual port used for the HTTP service For example to run the server on port 6080 define portbase as 6000 We use a portbase in place of an absolute address so that multiple protocols e g the FTP server embedded into Xitami can be managed as one unit Default 0 zero portbase n Specifies one or more alternate portbases if the primary HTTP port is unavailable will try portbase1 portbase2 etc until a free port is found or no further alternate portbases are found Default no default base host Specifies the name of the configuration file used for the base virtual host You may need this option when you have virtual hosts that all inherit values from defaults cfg but where the base host needs different values Default basehost cfg hostname Specifies your fully qualified domain name for the server This name is used whenever the server needs to redirect a request e g for image maps You may want to provide this when configuring a virtual host It is not usually necessary on single hosted systems Default the system hostname defaults Specifies the name of the local configuration file This file provides the defaults that are used for all virtual hosts Anything in the defaults file overrides the contents of xitami cfg Default defaults cfg The Alias Section This section lets you define multiple document roots Each alias specifies a name and a path For example Alias cdrom G html private pub i pub private doc i docs current The alias name may contain It is not case sensitive In A URL the alias comes at the start e g http 127 0 0 1 cdrom index htm There is no fixed limit to the number of aliases you can define However if you define large numbers of aliases Xitami will run slower An alias can refer to a file including extension In this case the file will act as a default file for that alias The Virtual Hosts Section This section lets you define virtual hosts A virtual host can be specified in two ways by IP address if your system has multiple IP addresses or by name if your system has multiple names Each entry in the Virtual Hosts section defines one virtual host like this Virtual Hosts www rnd imatix com research cfg 253 112 23 51 home cfg See the section on virtual hosts for more details The Filter Section This section is used to define filter programs Filters are programs that are run with the usually HTML file as input You can write filters in Perl Awk C Rexx or any other language that can handle standard input output streams Filters are a little like CGI programs except that they are invoked whenever a certain type of file is requested Each definition in this section consists of a file extension with a leading dot and a command The command may be with a full path or without if the program is on the PATH Xitami lets you run scripts directly under OS 2 and Windows 95 NT if you respect the header conventions noted in the CGI section You can pass any type of input file to a filter program with the restriction that it must be a text file Binary files will probably not work under MS DOS like file systems Under Unix there is no difference between text and binary files This is an example of the Filter section Filter ssi perlssi Pass ssi to the Perlssi filter The CGI Section This section controls the CGI protocol enabled Allows you to disable CGI handling in one stroke If this is 1 URLs that translate to a CGI are allowed If this is 0 URLs that translate to a CGI are rejected with a code 501 Not implemented Default 1 CGI is enabled workdir Defines the directory where CGI programs will run The web server must have write access to this directory You can tell Xitami to always use the script directory by specifying This is useful if you put scripts in various subdirectories This option applies to filters too Default script directory wildcard Defines whether the CGI URL indicator cgi bin is allowed anywhere in the URL or only at the start If 1 it is allowed anywhere in the URL If 0 it may come only at the start of the URL Note that setting this to 1 opens a significant security hole if you also allow people to FTP files into the HTTP area As soon as someone creates a directory called cgi bin they can upload and execute CGI programs In some configurations this is desirable In other configurations e g if you allow your users to upload CGI scripts or if you do not do FTP uploads into the HTTP space it can be desirable Default 0 cgi bin matches only at the start of the URL timeout The maximum time in seconds that a CGI program may run This option prevents looping CGI programs from blocking the server system for more than a short period However you will want to tune it if you run exceptionally slow CGIs e g large database searches Which we do not recommend you should always aim for a response time of less than 2 seconds and 5 seconds for heavy processing If you set this to zero Xitami lets CGIs run for an arbitrarily long time actually one hour before killing them Default 60 monitor The frequency in milliseconds at which Xitami monitors the progress of CGI programs If you raise this time to 500 for example Xitami will check the CGI program s progress every 1 2 second Anything less than 100 is not a good idea probably since it will slow down the server Default 200 dirlist If 1 the server will generate a directory listing for any URL that refers to a CGI directory not containing a default file If 0 such accesses result in a 403 Forbidden response Default 0 listings are allowed msdos style If 1 CGI programs and scripts get all filenames passed through the environment and on the command line in MS DOS format using backslashes otherwise they get filenames in Unix format using forward slashes Default 0 debug If 1 the server creates files containing the CGI input and output streams called tmp xxxxx cgi and tmp xxxxx cgo You can use these to debug CGI programs output Default 0 no debugging output stdio If 1 the server uses standard input output streams to pass CGI input and output data This is suitable for languages such as C Perl etc that have access to stdin and stdout streams When using languages that cannot read from stdin or write to stdout you must set this value to 0 and refer to the CGI STDIN and CGI STDOUT environment variables Default 1 use standard i o streams mixed url If 1 allows images HTML and other files in the cgi bin directory The CGI program can refer to these using relative addressing If 0 such files are not permitted Note that in any case executable files such as Perl scripts are always executed never downloaded Default 1 non executable files may be placed in cgi bin errlog Specifies a filename for output of CGI program errors A CGI program can send error messages to the stderr stream these are captured in this log file Default Empty no logging of CGI errors environment If 1 the CGI program gets the full web server environment including values such as PATH If 0 does not have access to such data The environment data can assist a hostile attack on the host system Default 1 server environment is supplied http fields Defines whether the HTTP request header fields are passed to the CGI program or not Default 1 HTTP header fields are supplied http prefix Specifies the prefix used to identify HTTP header fields in the CGI program environment Note that this should be different from the form prefix so that there is no chance of an overlap in field names To specify no prefix use http prefix Default HTTP form fields If 1 the form data coming from a GET or POST method is supplied as environment variables This can be required by some CGI programs However when large forms are used this may cause the environment to be over filled Since the form data is also available to the CGI program on its standard input device it can be useful to set this option to 0 Default 1 form data is included in environment form prefix Specifies the prefix used to identify form data fields in the CGI program environment To specify no prefix use form prefix Default FORM form query If 1 the form data coming from a POST method is supplied as the environment variable QUERY STRING If 0 this data is supplied as separate environment variables and on the standard input device but not as a QUERY STRING environment variable Some CGI products we know of Progress Webspeed will barf if this is turned on since they do not expect input in both this string and on stdin Default 0 form data is not included in QUERY STRING The CGI Environment Section This section is used to define specific CGI environment variables Each definition is taken literally and passed to the CGI program This can be useful when using virtual hosts For example CGI Environment HOSTNAME sales The CGI Alias Section This section lets you define multiple CGI program roots Each alias specifies a name and a path For example CGI Alias demos G site demos The alias name may contain It is not case sensitive In A URL the alias comes at the start e g http 127 0 0 1 demos calendar The Lrwp Section This section controls the LRWP long running web process protocol enabled Specifies whether the LRWP agent is enabled or not Default 1 port Specifies the port on which the LRWP agent accepts connections Default 81 webmask Specifies the webmask for LRWP clients Normally this is restricted to local LRWP clients but you can also construct LRWP networks from multiple servers Use webmask local to specify just local addresses or webmask item item to specify one or more types of access Each item allows or excludes some IP address es 250 12 13 allows matching addresses 250 12 13 excludes matching addresses but does not allow others 250 12 13 excludes one set of addresses and allows all others webmask iplist txt reads the list of webmasks from a text file More information is available Default local allow all Allows all LRWP clients to connect If this is set to 1 any LRWP application will be allowed to connect Otherwise the LRWP Application section must be used to authorise specific applications and optionally specify a password to use during the authentication stage Default 1 The Lrwp Application Section This section consists of one entry per application name either URL prefix or a URL extension name The entry should either to be set to to indicate the application is allowed without authentication or to a password phrase that is used in LRWP 2 0 authentication with that application If a password phrase is specified then LRWP 1 0 clients will not be allowed to connect with that name as they cannot perform the required authentication This is an example of enties in the Lrwp Application section LRWP Application testapp Connect without any password secureapp funky161 Connect using secure password The Security Section This section defines HTTP server security options filename Specifies the Basic Authentication file Default xitami aut password case If 1 passwords are case sensitive If 0 passwords are always converted to lower case before validation If you set this to 0 be sure to use lower case passwords in the password file Default 1 case sensitive dirlist If 1 the server will generate a directory listing for any URL that refers to a directory not containing a default file If 0 such accesses result in a 403 Forbidden response Default 1 listings are allowed admin If 1 the server will allow access to the web based administration pages WBA If 0 the WBA agent will not be started This is a safe way to disable WBA access for sites where this is not needed and poses a potential security hole Default 1 WBA is enabled superuser Specifies the Superuser password If this is or no superuser access is allowed Anything else is accepted as a password for all protected resources including the online administration functions This password overrides the webmask for any resource So be really careful Okay I warned you It does not override the webmask for the entire server Default disabled safepaths If 1 the server will refuse access to unsafe URLs which is a notion that Microsoft invented when they allowed the same file to have a short and a long filename When this is enabled Xitami rejects any URLs that contain a directory name which can be translated to a different long name and the user receives a 403 error message If 0 this check is not done Default 1 security check is enabled webmask Limits the set of clients that can connect to the server This is meant to provide an easy way of creating an internal web service The web mask is one or more patterns each of which specifies some valid or excluded addresses A pattern is some IP address in string format possibly with replacing part of the end of address For instance the pattern 250 12 13 restricts access to clients with IP addresses starting with 250 12 13 If you start a pattern with the pattern excludes

    Original URL path: http://allegro.hab.de/xitami/index4.htm (2016-02-14)
    Open archived version from archive

  • Using The Common Gateway Interface (CGI)
    to the input and output files Rexx programs The first line of the program must start with the characters followed by a space and the full filename for Rexx The exe extension is optional You can close the comment on the same line but the must be the last text on the line Batch files although their usefulness is limited since MS DOS has trouble with the HTML characters and com files should run correctly under 32 bit Windows We recommend that you use 32 bit executable programs also called console programs The Windows 32 bit interface is more robust and controlled than the 16 bit interface One example if a CGI program loops Xitami will kill it after a timeout But a 16 bit DOS program will not respond to a kill request and will eventually bring the system down CGI Programs Under UNIX Under UNIX you can run any file that UNIX recognizes as an executable file This includes linked files Perl scripts shell scripts etc CGI Programs Under OS 2 Under OS 2 you can run different types of CGI programs 32 bit and 16 bit command line based executable exe files You do not need to specify the exe file extension in the URL Xitami for OS 2 will correctly locate an exe CGI program Starting PM based executable files through CGI is not supported REXX and CMD scripts These files must have a cmd extension but this does not have to be specified in the URL unless there is an executable exe of the same name in the directory see the details of the search order below By default the script will be run by running the program specified in the COMSPEC environment variable followed by c scriptname so if your COMSPEC variable is set to d os2 cmd exe then it will be run as d os2 cmd exe c scriptname Optionally you can specify a different interpreter for the script by using either The OS 2 EXTPROC syntax EXTPROC full path to interpreter flags in the first line of the script file Xitami will accept flags at the end of the EXTPROC line by some other programs may not test carefully or A special REXX comment full path to interpreter flags in the first line of the script file You can use the standard OS 2 command interpreter CMD EXE as the interpreter for REXX but if you do then you must specify c as one of the flags to ensure the command interpreter exits as soon as the CGI script finishes running Remember the REXX scripts are identified by the comment in their first line The full path to interpreter should specify the full filename drive if it is not on the same drive as everything else path and filename of the interpreter to use Perl programs The first line of the program must start with the characters followed by a space and the full filename for Perl For example if your

    Original URL path: http://allegro.hab.de/xitami/index5.htm (2016-02-14)
    Open archived version from archive

  • Using SSI and Filters
    is a fairly standard syntax which you can read about on the NCSA site We implemented all the common SSI tags in the PerlSSI filter To use this you need Perl on your system it should be on the PATH The PerlSSI filter is slow and meant as a work around until we implement SSI the correct way in the server itself The PerlSSI filter is located in the Xitami directory itself To run it you must have Perl installed The requirements for this filter are the same as for a Perl CGI program By default Xitami recognises any document with extension ssi shtm or shtml as an SSI document This is defined in the Filters section of the configuration files The SSI documents are placed in the normal web pages directory and are recognised purely by their extension not the path Xitami supports these SSI tags Element syntax Effect config errmsg text Specify the SSI error message config sizefmt format Specify whether file sizes are shown in full or abbreviated Use the format abbrev to show abbreviated sizes config timefmt format Specify the format used for file times By default this is A d b y H M S Z Note the current implementation of SSI ignores the timefmt and always uses the default time format echo var variable Output the value of the specified variable Xitami recognises these variables DOCUMENT NAME DOCUMENT URI DATE GMT DATE LOCAL LAST MODIFIED and any environment variable including the standard CGI environment variables exec cgi pathname Outputs the result of the CGI program which must be in the CGI binary directory it cannot be on a CGI alias directory Note that the CGI program runs in the main Xitami directory exec cmd command Executes a native command and includes the output of

    Original URL path: http://allegro.hab.de/xitami/index6.htm (2016-02-14)
    Open archived version from archive

  • Image Maps
    of coordinates separated by spaces The URL can be any Internet URL either an absolute image map or a relative image map Xitami will recognise and handle these types of URLs A filename with no path Xitami prefixes the path of the image map file A filename with a path Xitami prefixes http the name of the server host and the port number if that is not 80 An absolute URL starting with http or another scheme such as mailto ftp etc You can use these elements types in the image map Element syntax Effect default url Defines the default URL for the image rect url x1 y1 x2 y2 Defines a rectangle between the two corner points specified Assumes x2 x1 y2 y1 circle url x1 y1 x2 y2 Defines a circle where x1 y1 is the circle s center and x2 y2 is any point on its circumference point url x y Defines a point Accepts a click within about 3 pixels of the point poly url x y Defines a polygon where x1 y1 xn yn defines the perimeter of the polygon You can specify up to 100 points There are many freely available tools to help

    Original URL path: http://allegro.hab.de/xitami/index7.htm (2016-02-14)
    Open archived version from archive

  • Virtual Hosts
    will accept connections on all ten A multihomed virtual host is identified by its IP address A DNS based virtual host is identified by its name Virtual Hosts xxx xxx xxx xxx filename cfg A multihomed host www some domain filename cfg A DNS based virtual host DNS based virtual hosting requires a DNS server or something similar The mechanisms for setting up both multiple IP addresses and multiple domain names are system specific you should have access to technical documentation for your TCP IP configuration or good technical support DNS based virtual hosting uses a HTTP 1 1 feature called the Host header and an FTP feature whereby the user name is specified as user hostname Most modern browsers support this if you are building an intranet it is quite easy to be sure that all browsers will work correctly with DNS based virtual hosting On the Internet you can catch browsers that do not send a valid Host header and show some specific pages The SSL protocol used in Xitami Pro cannot work with DNS based virtual hosts so to use SSL virtual hosts you must have a unique IP address for each host When you set up a virtual host you will generally want to use a specific directory for the web pages CGI scripts password file and log files You can also share these in any way you need to You can also configure options such as the HTTP error messages timeouts security and so on To define these you specify a configuration file per virtual host The virtual host configuration inherits all definitions from defaults cfg and xitami cfg You need only define those options that are specific to the virtual host If the HTTP request refers to a host name or IP address that has not been configured as a virtual host the request is handled by the base host To configure the base host create a file called basehost cfg You can change this name in the defaults cfg file server base host option This is a typical configuration for a site with several virtual hosts Server webpages websites hostx webpages cgi bin websites hostx cgi bin Some of the options in the Server apply to the entire server globally and are not taken from the virtual host configuration file background customise debug limit portbase and refresh When you define a multihomed virtual host you must specify a server hostname value This should be a host name that translates back into the correct IP address The server hostname option is used whenever Xitami has to return a redirected URL for image maps incomplete URL and directory listings If you do not define server hostname or define it wrongly these functions may not work When you define a DNS based virtual host Xitami takes the name as a default value for the server hostname option This usually works correctly but you can override it if necessary by adding the server hostname option explicitly To

    Original URL path: http://allegro.hab.de/xitami/index8.htm (2016-02-14)
    Open archived version from archive

  • The FTP Service
    case If 1 FTP passwords are case sensitive If 0 passwords are always converted to lower case before validation If you set this to 0 be sure to use only lower case passwords in the password file Default 1 case sensitive data port Specifies the port at which data connections will be made Xitami scans for free ports so this is simply the start of a range of ports The port is shifted by whatever value was used for the server portbase Default 200 force ip Indicates whether passive connections must be forced to the IP address specified in the ipaddress option Default 0 do not force ipaddress The IP address used for passive connections If accepts passive connections on all local available IP addresses Default The FTPLog Section This section controls the FTP access log enabled Specifies whether FTP accesses are logged or not FTP accesses are logged in a format similar to that used for HTTP accesses Default 1 accesses are logged filename Specifies the filename for access logging This may be the same as the main HTTP access log file Default access log Specifies the cycle mode for the log file Can be one of startup or 0 cycle log when the server is starts hourly or 1 cycle log each hour daily or 2 cycle log each day weekly or 3 cycle log each week monthly or 4 cycle log each month or manual or 5 manual cycling only Default daily local Specifies whether to include local addresses or not Default 1 include local addresses The FTP Alias Section This section lets you define multiple FTP file roots Each alias alias specifies a name and a path For example FTP Alias volume c C The alias name itself may not contain It is not case sensitive FTP aliases are only shown to root users i e those with an empty root value or those who have the aliases 1 option defined see below Like HTTP aliases the FTP alias is always the first component of a filename e g volume c somefile Aliases are shown only if the user has no GET access and if the specified user s root directory actually exists The FTPErrLog Section This section controls the FTP error log enabled Specifies whether FTP errors are logged or not FTP errors are logged in a format similar to that used for HTTP errors Default 1 errors are logged filename Specifies the filename for error logging This may be the same as the main HTTP error log file Default error log Specifies the cycle mode for the log file Can be one of startup or 0 cycle log when the server is starts hourly or 1 cycle log each hour daily or 2 cycle log each day weekly or 3 cycle log each week monthly or 4 cycle log each month or manual or 5 manual cycling only Default daily local Specifies whether to include local addresses or not Default 1 include local addresses

    Original URL path: http://allegro.hab.de/xitami/index9.htm (2016-02-14)
    Open archived version from archive

  • A Beginner's Guide
    com To connect your computer to a network you need to give it a fixed IP address and a domain name This is a job for a network administrator On a dial up PPP connection you get a temporary IP address which can be used eg http 193 23 54 12 but it changes each time you connect Some providers will give you a fixed IP address sometimes at extra cost Getting Yourself Connected This section describes how to make your web site available to other people The problems involved in connecting on an internal network are a little different from connecting to the Internet itself How Do Domain Names Work So long as you have TCP IP installed and running you can use 127 0 0 1 and localhost which both mean the same normally and which TCP IP interprets as the loopback address i e the current machine When you want to talk to other computers you need to know their IP address Correspondingly your system also needs an IP address And your address has to be unique network wide When the network is the Internet this means world wide There are two ways to get such a unique address One you ask pay someone for a fixed address Two you work with an ISP that owns a pool of addresses This is typically how dial up PPP connections work the ISP will lend you an address for the duration of the connection Now if you dial up on a PPP line and you do ping xxxx where xxxx is the name of your system ping will tell you your current IP address Other people can then connect to that address and access your web pages This works But they have to type the literal address xxx xxx xxx xxx TCP IP uses a system called DNS to translate a name like imatix com into an address DNS uses a network of servers that are able to translate names into addresses So when you use Netscape to access imatix com your local TCP IP interface asks its local DNS server to translate the name This goes off and after several hops comes back with the address and then you can connect The system name must of course be unique within the network or world wide on the Internet Again you can get unique names in several ways You can extend an existing domain name research imatix com or invent a new domain name some thing com Domain names must be registered with the Internic This costs 70 for 2 years and 35 per year after that You can do this directly or via your ISP It s quite a fast process the only problem is finding a good domain name that s not already used In general you ll find that a dial up PPP connection is not much use for a web server since your IP address changes each time you dial in to your ISP Ignoring the fact that local phone calls still cost quite a lot in many parts of the world There are some interesting sites that help get around this problem by acting as DNS proxy servers for such connections If you want to do this kind of thing you ll have to investigate yourself we re getting too deep for a beginner s guide On An Intranet LAN See your network administrator to get an IP address Then configure your TCP IP software so that your computer is reachable from others on the network Generally you ll already have got TCP IP working even to run Xitami on a stand alone system What changes with respect to an intranet is that you need an IP address and it can t be the same as any other IP address on the network When TCP IP is working correctly even before you start Xitami you can use the ping command from other machines to check that your machine is addressable Type ping like this ping xxx xxx xxx xxx Where xxx xxx xxx xxx is the IP address of your machine If this works then you can start Xitami and access it from a browser using the URL http xxx xxx xxx xxx The next step is to get your system known by the DNS domain name system An intranet usually has one or two domain name servers although it s not mandatory If DNS is working you can configure your TCP IP to talk to the DNS server then other PCs will be able to refer to your system by name not IP address If you do not have a DNS server you can generally use the hosts file in Windows this sites in C Windows to translate IP addresses into names and vice versa Each computer that want to access your web site needs to put a line in its hosts file This is a bit tedious which is why DNS exists On The Big Wide World Wide Web Getting your site onto the web involves cooperation from a commercial provider of some sorts You can get help from Your ISP who can provide a fixed line or a permanent IP address for dial up connections or space and a connection for your own server PC A virtual host provider who can provide a complete web site although then you are normally not using your own machine A telecoms operator who can provide you with a high speed link to one of the Internet backbones A good solution for a small web site is to pay for a fixed line There are various technologies ISDN ASDL POTS plain old telephone something Check out the capacity of the line and shop around for the best deal This gives you the most flexibility and control of your system but may be limited when handling large volumes The most interesting type of connection may be the kind offered by TV cable companies in some cities

    Original URL path: http://allegro.hab.de/xitami/index10.htm (2016-02-14)
    Open archived version from archive



  •