archive-be.com » BE » F » FACILITEURSFINANCIERS.BE

Total: 153

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

Or switch to "Titles and links view".
  • Test Page for the SSL/TLS-aware Apache Installation on Web Site
    replace this placeholder page or else point the server at their real content ATTENTION If you are seeing this page instead of the site you expected please contact the administrator of the site involved Try sending mail to webmaster domain Although this site is running the Apache software it almost certainly has no other connection to the Apache Group so please do not send mail about this site or its

    Original URL path: http://www.faciliteursfinanciers.be/ (2012-07-05)
    Open archived version from archive

  • Apache HTTP Server Version 1.3 Documentation
    and Installing Starting Stopping or Restarting Run time Configuration Directives Modules By Type or Alphabetical Server and Supporting Programs Dynamic Shared Object DSO Support The Apache API Platform Specific Notes Microsoft Windows Cygwin Novell Netware HP MPE iX UnixWare TPF Using the Apache HTTP Server Authentication Authorization and Access Control CGI Dynamic Content with CGI Configuration Files Content negotiation Environment Variables General Performance hints Handlers Log Files Security tips Server

    Original URL path: http://www.faciliteursfinanciers.be/manual/index.html (2012-07-05)
    Open archived version from archive

  • mod_ssl: Title Page
    mod ssl version 2 8 Ralf S Engelschall rse engelschall com www engelschall com Overview

    Original URL path: http://www.faciliteursfinanciers.be/manual/mod/mod_ssl/ (2012-07-05)
    Open archived version from archive

  • Apache Server Frequently Asked Questions
    Your Group directive probably in conf httpd conf needs to name a group that actually exists in the etc group file or your system s equivalent This problem is also frequently seen when a negative number is used in the Group directive e g Group 1 Using a group name not group number found in your system s group database should solve this problem in all cases Why am I getting httpd could not set socket option TCP NODELAY in my error log This message almost always indicates that the client disconnected before Apache reached the point of calling setsockopt for the connection It shouldn t occur for more than about 1 of the requests your server handles and it s advisory only in any case Why am I getting connection reset by peer in my error log This is a normal message and nothing about which to be alarmed It simply means that the client canceled the connection before it had been completely set up such as by the end user pressing the Stop button People s patience being what it is sites with response time problems or slow network links may experience this more than high capacity ones or those with large pipes to the network The errorlog says Apache dumped core but where s the dump file In Apache version 1 2 the error log message about dumped core includes the directory where the dump file should be located However many Unixes do not allow a process that has called setuid to dump core for security reasons the typical Apache setup has the server started as root to bind to port 80 after which it changes UIDs to a non privileged user to serve requests Dealing with this is extremely operating system specific and may require rebuilding your system kernel Consult your operating system documentation or vendor for more information about whether your system does this and how to bypass it If there is a documented way of bypassing it it is recommended that you bypass it only for the httpd server process if possible The canonical location for Apache s core dump files is the ServerRoot directory As of Apache version 1 3 the location can be set via the CoreDumpDirectory directive to a different directory Make sure that this directory is writable by the user the server runs as as opposed to the user the server is started as When I run it under Linux I get shmget function not found what should I do Your kernel has been built without SysV IPC support You will have to rebuild the kernel with that support enabled it s under the General Setup submenu Documentation for kernel building is beyond the scope of this FAQ you should consult the Kernel HOWTO or the documentation provided with your distribution or a Linux newsgroup mailing list As a last resort workaround you can comment out the define USE SHMGET SCOREBOARD definition in the LINUX section of src conf h and rebuild the server prior to 1 3b4 simply removing define HAVE SHMGET would have sufficed This will produce a server which is slower and less reliable Server hangs or fails to start and or error log fills with fcntl F SETLKW No record locks available or similar messages These are symptoms of a fine locking problem which usually means that the server is trying to use a synchronization file on an NFS filesystem Because of its parallel operation model the Apache Web server needs to provide some form of synchronization when accessing certain resources One of these synchronization methods involves taking out locks on a file which means that the filesystem whereon the lockfile resides must support locking In many cases this means it can t be kept on an NFS mounted filesystem To cause the Web server to work around the NFS locking limitations include a line such as the following in your server configuration files LockFile var run apache lock The directory should not be generally writable e g don t use var tmp See the LockFile documentation for more information Why am I getting Expected Directory but saw Directory when I try to start Apache This is a known problem with certain versions of the AIX C compiler IBM are working on a solution and the issue is being tracked by problem report 2312 I m using RedHat Linux and I have problems with httpd dying randomly or not restarting properly RedHat Linux versions 4 x and possibly earlier RPMs contain various nasty scripts which do not stop or restart Apache properly These can affect you even if you re not running the RedHat supplied RPMs If you re using the default install then you re probably running Apache 1 1 3 which is outdated From RedHat s ftp site you can pick up a more recent RPM for Apache 1 2 x This will solve one of the problems If you re using a custom built Apache rather than the RedHat RPMs then you should rpm e apache In particular you want the mildly broken etc logrotate d apache script to be removed and you want the broken etc rc d init d httpd or httpd init script to be removed The latter is actually fixed by the apache 1 2 5 RPMs but if you re building your own Apache then you probably don t want the RedHat files We can t stress enough how important it is for folks especially vendors to follow the stopping Apache directions given in our documentation In RedHat s defense the broken scripts were necessary with Apache 1 1 x because the Linux support in 1 1 x was very poor and there were various race conditions on all platforms None of this should be necessary with Apache 1 2 and later I upgraded from an Apache version earlier than 1 2 0 and suddenly I have problems with Apache dying randomly or not restarting properly You should read the previous note about problems with RedHat installations It is entirely likely that your installation has start stop restart scripts which were built for an earlier version of Apache Versions earlier than 1 2 0 had various race conditions that made it necessary to use kill 9 at times to take out all the httpd servers But that should not be necessary any longer You should follow the directions on how to stop and restart Apache As of Apache 1 3 there is a script src support apachectl which after a bit of customization is suitable for starting stopping and restarting your server When I try to start Apache from a DOS window I get a message like Cannot determine host name Use ServerName directive to set it manually What does this mean It means what it says the Apache software can t determine the hostname of your system Edit your conf httpd conf file look for the string ServerName and make sure there s an uncommented directive such as ServerName localhost or ServerName www foo com in the file Correct it if there one there with wrong information or add one if you don t already have one Also make sure that your Windows system has DNS enabled See the TCP IP setup component of the Networking or Internet Options control panel After verifying that DNS is enabled and that you have a valid hostname in your ServerName directive try to start the server again When I try to start Apache for Windows I get a message like Unable To Locate WS2 32 DLL What should I do Short answer You need to install Winsock 2 available from http www microsoft com windows95 downloads Detailed answer Prior to version 1 3 9 Apache for Windows used Winsock 1 1 Beginning with version 1 3 9 Apache began using Winsock 2 features specifically WSADuplicateSocket WS2 32 DLL implements the Winsock 2 API Winsock 2 ships with Windows NT 4 0 and Windows 98 Some of the earlier releases of Windows 95 did not include Winsock 2 Apache for Windows does not start Error log contains this message crit 10045 The attempted operation is not supported for the type of object referenced Parent WSADuplicateSocket failed for socket What does this mean We have seen this problem when Apache is run on systems along with Virtual Private Networking clients like Aventail Connect Aventail Connect is a Layered Service Provider LSP that inserts itself as a shim between the Winsock 2 API and Window s native Winsock 2 implementation The Aventail Connect shim does not implement WSADuplicateSocket which is the cause of the failure The shim is not unloaded when Aventail Connect is shut down Once observed the problem persists until the shim is either explicitly unloaded or the machine is rebooted Another potential solution not tested is to add apache exe to the Aventail Connect Exclusion List Apache is affected in a similar way by any firewall program that isn t correctly configured Assure you exclude your Apache server ports usually port 80 from the list of ports to block Refer to your firewall program s documentation for the how to When I try to start Apache on Windows I get a message like System error 1067 has occurred The process terminated unexpectedly What does this mean This message means that the Web server was unable to start correctly for one reason or another To find out why execute the following commands in a DOS window c cd Program Files Apache Group Apache apache If you don t get the prompt back hit Control C to cause Apache to exit The error you see will probably be one of those preceding this question in the FAQ As of Apache 1 3 14 first check the Windows NT Event Log for Application errors using the Windows NT 2000 Event Viewer program Any errors that occur prior to opening the Apache error log will be stored here if Apache is run as a Service on NT or 2000 As with any error also check your Apache error log On a SuSE Linux system I try and configure access control using basic authentication Although I follow the example exactly authentication fails and an error message admin not a valid FDN is logged In the SuSE distribution additional 3rd party authentication modules have been added and activated by default These modules interfere with the Apache standard modules and cause Basic authentication to fail Our recommendation is to comment all those modules in etc httpd suse addmodule conf and etc httpd suse loadmodule conf which are not actually required for running your server Why do I have weird entries in my logs asking for default ida and cmd exe The host requesting pages from your website and creating those entries is a Windows machine running IIS that has been infected by an Internet worm such as Nimda or Code Red You can safely ignore these error messages as they do not affect Apache ApacheWeek has an article with more information Why am I getting server restart messages periodically when I did not restart the server Problem You are noticing restart messages in your error log periodically when you know you did not restart the server yourself Thu Jun 6 04 02 01 2002 notice SIGHUP received Attempting to restart Thu Jun 6 04 02 02 2002 notice Apache configured resuming normal operations Check your cron jobs to see when if your server logs are being rotated Compare the time of rotation to the error message time If they are the same you can somewhat safely assume that the restart is due to your server logs being rotated Why am I getting module module name is not compatible with this version of Apache messages in my error log Module Magic Number MMN is a constant defined in Apache source that is associated with binary compatibility of modules It is changed when internal Apache structures function calls and other significant parts of API change in such a way that binary compatibility cannot be guaranteed any more On MMN change all third party modules have to be at least recompiled sometimes even slightly changed in order to work with the new version of Apache If you re getting the above error messages contact the vendor of the module for the new binary or compile it if you have access to the source code E Configuration Questions Why can t I run more than n virtual hosts You are probably running into resource limitations in your operating system The most common limitation is the per process limit on file descriptors which is almost always the cause of problems seen when adding virtual hosts Apache often does not give an intuitive error message because it is normally some library routine such as gethostbyname which needs file descriptors and doesn t complain intelligibly when it can t get them Each log file requires a file descriptor which means that if you are using separate access and error logs for each virtual host each virtual host needs two file descriptors Each Listen directive also needs a file descriptor Typical values for n that we ve seen are in the neighborhood of 128 or 250 When the server bumps into the file descriptor limit it may dump core with a SIGSEGV it might just hang or it may limp along and you ll see possibly meaningful errors in the error log One common problem that occurs when you run into a file descriptor limit is that CGI scripts stop being executed properly As to what you can do about this Reduce the number of Listen directives If there are no other servers running on the machine on the same port then you normally don t need any Listen directives at all By default Apache listens to all addresses on port 80 Reduce the number of log files You can use mod log config to log all requests to a single log file while including the name of the virtual host in the log file You can then write a script to split the logfile into separate files later if necessary Such a script is provided with the Apache 1 3 distribution in the src support split logfile file Increase the number of file descriptors available to the server see your system s documentation on the limit or ulimit commands For some systems information on how to do this is available in the performance hints page There is a specific note for FreeBSD below For Windows 95 try modifying your C CONFIG SYS file to include a line like FILES 300 Remember that you ll need to reboot your Windows 95 system in order for the new value to take effect Don t do that try to run with fewer virtual hosts Spread your operation across multiple server processes using Listen for example but see the first point and or ports Since this is an operating system limitation there s not much else available in the way of solutions As of 1 2 1 we have made attempts to work around various limitations involving running with many descriptors More information is available Can I increase FD SETSIZE on FreeBSD On versions of FreeBSD before 3 0 the FD SETSIZE define defaults to 256 This means that you will have trouble usefully using more than 256 file descriptors in Apache This can be increased but doing so can be tricky If you are using a version prior to 2 2 you need to recompile your kernel with a larger FD SETSIZE This can be done by adding a line such as options FD SETSIZE nnn to your kernel config file Starting at version 2 2 this is no longer necessary If you are using a version of 2 1 stable from after 1997 03 10 or 2 2 or 3 0 current from before 1997 06 28 there is a limit in the resolver library that prevents it from using more file descriptors than what FD SETSIZE is set to when libc is compiled To increase this you have to recompile libc with a higher FD SETSIZE In FreeBSD 3 0 the default FD SETSIZE has been increased to 1024 and the above limitation in the resolver library has been removed After you deal with the appropriate changes above you can increase the setting of FD SETSIZE at Apache compilation time by adding DFD SETSIZE nnn to the EXTRA CFLAGS line in your Configuration file Why doesn t my ErrorDocument 401 work You need to use it with a URL in the form foo bar and not one with a method and hostname such as http host foo bar See the ErrorDocument documentation for details This was incorrectly documented in the past Why does Apache send a cookie on every response Apache does not automatically send a cookie on every response unless you have re compiled it with the mod usertrack module and specifically enabled it with the CookieTracking directive This module has been in Apache since version 1 2 This module may help track users and uses cookies to do this If you are not using the data generated by mod usertrack do not compile it into Apache Why don t my cookies work I even compiled in mod cookies Firstly you do not need to compile in mod cookies in order for your scripts to work see the previous question for more about mod cookies Apache passes on your Set Cookie header fine with or without this module If cookies do not work it will be because your script does not work properly or your browser does not use cookies or is not set up to accept them Why do my Java app let s give me plain text when I request an URL from an Apache server As of version 1 2 Apache is an HTTP 1 1 HyperText Transfer Protocol version 1 1 server This fact is reflected in the protocol version that s included in the response headers sent to a client when processing a request Unfortunately low level Web access classes included in the Java Development Kit JDK version 1 0 2 expect to see the version string HTTP 1 0 and do not correctly interpret the HTTP 1 1 value Apache is sending this part of the response is a declaration of what the server can do rather than a declaration of the dialect of the response The result is that the JDK methods do not correctly parse the headers and include them with the document content by mistake This is definitely a bug in the JDK 1 0 2 foundation classes from Sun and it has been fixed in version 1 1 However the classes in question are part of the virtual machine environment which means they re part of the Web browser if Java enabled or the Java environment on the client system so even if you develop your classes with a recent JDK the eventual users might encounter the problem The classes involved are replaceable by vendors implementing the Java virtual machine environment and so even those that are based upon the 1 0 2 version may not have this problem In the meantime a workaround is to tell Apache to fake an HTTP 1 0 response to requests that come from the JDK methods this can be done by including a line such as the following in your server configuration files BrowserMatch Java1 0 force response 1 0 BrowserMatch JDK 1 0 force response 1 0 More information about this issue can be found in the Java and HTTP 1 1 page at the Apache web site How do I get Apache to send a MIDI file so the browser can play it Even though the registered MIME type for MIDI files is audio midi some browsers are not set up to recognize it as such instead they look for audio x midi There are two things you can do to address this Configure your browser to treat documents of type audio midi correctly This is the type that Apache sends by default This may not be workable however if you have many client installations to change or if some or many of the clients are not under your control Instruct Apache to send a different Content type header for these files by adding the following line to your server s configuration files AddType audio x midi mid midi kar Note that this may break browsers that do recognize the audio midi MIME type unless they re prepared to also handle audio x midi the same way How do I add browsers and referrers to my logs Apache provides a couple of different ways of doing this The recommended method is to compile the mod log config module into your configuration and use the CustomLog directive You can either log the additional information in files other than your normal transfer log or you can add them to the records already being written For example CustomLog logs access log h l u t r s b Referer i User Agent i This will add the values of the User agent and Referer headers which indicate the client and the referring page respectively to the end of each line in the access log You may want to check out the Apache Week article entitled Gathering Visitor Information Customizing Your Logfiles Why does accessing directories only work when I include the trailing e g http foo domain com user but not when I omit it e g http foo domain com user When you access a directory without a trailing Apache needs to send what is called a redirect to the client to tell it to add the trailing slash If it did not do so relative URLs would not work properly When it sends the redirect it needs to know the name of the server so that it can include it in the redirect There are two ways for Apache to find this out either it can guess or you can tell it If your DNS is configured correctly it can normally guess without any problems If it is not however then you need to tell it Add a ServerName directive to the config file to tell it what the domain name of the server is The other thing that can occasionally cause this symptom is a misunderstanding of the Alias directive resulting in an alias working with a trailing slash and not without one The Alias directive is very literal and aliases what you tell it to Consider the following example Alias example home www example The above directive creates an alias for URLs starting with example but does not alias URLs starting with example That is to say a URL such as http servername com example will get the desired content but a URL such as http servername com example will result in a file not found error The following Alias on the other hand will work for both cases Alias example home www example Why doesn t mod info list any directives The mod info module allows you to use a Web browser to see how your server is configured Among the information it displays is the list modules and their configuration directives The current values for the directives are not necessarily those of the running server they are extracted from the configuration files themselves at the time of the request If the files have been changed since the server was last reloaded the display will not match the values actively in use If the files and the path to the files are not readable by the user as which the server is running see the User directive then mod info cannot read them in order to list their values An entry will be made in the error log in this event however I upgraded to Apache 1 3 and now my virtual hosts don t work In versions of Apache prior to 1 3b2 there was a lot of confusion regarding address based virtual hosts and HTTP 1 1 name based virtual hosts and the rules concerning how the server processed VirtualHost definitions were very complex and not well documented Apache 1 3b2 introduced a new directive NameVirtualHost which simplifies the rules quite a bit However changing the rules like this means that your existing name based VirtualHost containers probably won t work correctly immediately following the upgrade To correct this problem add the following line to the beginning of your server configuration file before defining any virtual hosts NameVirtualHost n n n n Replace the n n n n with the IP address to which the name based virtual host names resolve if you have multiple name based hosts on multiple addresses repeat the directive for each address Make sure that your name based VirtualHost blocks contain ServerName and possibly ServerAlias directives so Apache can be sure to tell them apart correctly Please see the Apache Virtual Host documentation for further details about configuration I m using RedHat Linux and my htm files are showing up as HTML source rather than being formatted RedHat messed up and forgot to put a content type for htm files into etc mime types Edit etc mime types find the line containing html and add htm to it Then restart your httpd server kill HUP cat var run httpd pid Then clear your browsers caches Many browsers won t re examine the content type after they ve reloaded a page My htaccess files are being ignored This is almost always due to your AllowOverride directive being set incorrectly for the directory in question If it is set to None then htaccess files will not even be looked for If you do have one that is set then be certain it covers the directory you are trying to use the htaccess file in This is normally accomplished by ensuring it is inside the proper Directory container Why do I get a Forbidden message whenever I try to access a particular directory This message is generally caused because either The underlying file system permissions do not allow the User Group under which Apache is running to access the necessary files or The Apache configuration has some access restrictions in place which forbid access to the files You can determine which case applies to your situation by checking the error log In the case where file system permission are at fault remember that not only must the directory and files in question be readable but also all parent directories must be at least searchable i e chmod x directory path by the web server in order for the content to be accessible Why do I get a Forbidden You don t have permission to access on this server message whenever I try to access my server Search your conf httpd conf file for this exact string Files If you find it that s your problem that particular Files container is malformed Delete it or replace it with Files ht and restart your server and things should work as expected This error appears to be caused by a problem with the version of linuxconf distributed with Redhat 6 x It may reappear if you use linuxconf again If you don t find this string check out the previous question Why do my files appear correctly in Internet Explorer but show up as source or trigger a save window with Netscape or Why doesn t Internet Explorer render my text plain document correctly MS Internet Explorer MSIE and Netscape handle mime type detection in different ways and therefore will display the document differently In particular IE sometimes relies on the file extension or the contents of the file to determine the mime type This can happen when the server specifies a mime type of application octet stream or text plain This behavior violates the the HTTP standard and makes it impossible to deliver plain text documents to MSIE clients in some cases More details are available on MSIE s mime type detection behavior in an MSDN article and a note by Alan J Flavell The best you can do as a server administrator is to accurately configure the mime type of your documents by editing the mime types file or using an AddType directive in the Apache configuration files In some cases you may be able to fool MSIE into rendering text plain documents correctly by assuring they have a txt filename extension but this will not work if MSIE thinks the content looks like another file type My site is accessible under many different hostnames how do I redirect clients so that they see only a single name Many sites map a variety of hostnames to the same content For example www example com example com and www example net may all refer to the same site It is best to make sure that regardless of the name clients use to access the site they will be redirected to a single canonical hostname This makes the site easier to maintain and assures that there will be only one version of the site in proxy caches and search engines There are two techniques to implement canonical hostnames Use mod rewrite as described in the Canonical Hostnames section of the URL Rewriting Guide Use name based virtual hosting NameVirtualHost VirtualHost ServerName www example net ServerAlias example com Redirect permanent http www example com VirtualHost VirtualHost ServerName www example com DocumentRoot usr local apache htdocs VirtualHost Why can I access my website from the server or from my local network but I can t access it from elsewhere on the Internet There are many possible reasons for this and almost all of them are related to the configuration of your network not the configuration of the Apache HTTP Server One of the most common problems is that a firewall blocks access to the default HTTP port 80 In particular many consumer ISPs block access to this port You can see if this is the case by changing any Port and Listen directives in httpd conf to use port 8000 and then request your site using http yourhost example com 8000 Of course a very restrictive firewall may block this port as well How do I turn automatic directory listings on or off If a client requests a URL that designates a directory and the directory does not contain a filename that matches the DirectoryIndex directive then mod autoindex can be configured to present a listing of the directory contents To turn on automatic directory indexing find the Options directive that applies to the directory and add the Indexes keyword For example Directory path to directory Options Indexes Directory To turn off automatic directory indexing remove the Indexes keyword from the appropriate Options line To turn off directory listing for a particular subdirectory you can use Options Indexes For example Directory path to directory Options Indexes Directory Why do my Options directives not have the desired effect Directives placed in the configuration files are applied in a very particular order as described by How Directory Location and Files sections work In addition each Options directive has the effect of resetting the options to none before adding the specified options unless only and options are used The consequence is that Options set in the main server or virtual host context outside any directory location or files section will usually have no effect because they are overridden by more specific Options directives For example in the following Directory usr local apache htdocs Options Indexes Directory Options Includes ExecCGI Includes and ExecCGI will be off in the usr local apache htdocs directory You can usually avoid problems by either finding the Options directive that already applies to a specific directory and changing it or by putting your Options directive inside the most specific possible Directory section How can I change the information that Apache returns about itself in the headers When a client connects to Apache part of the information returned in the headers is the name Apache Additional information that can be sent is the version number such as 1 3 26 the operating system and a list of non standard modules you have installed For example Server Apache 1 3 26 Unix mod perl 1 26 Frequently people want to remove this information under the mistaken understanding that this will make the system more secure This is probably not the case as the same exploits will likely be attempted regardless of the header information you provide There are however two answers to this question the correct answer and the answer that you are probably looking for The correct answer to this question is that you should use the ServerTokens directive to alter the quantity of information which is passed in the headers Setting this directive to Prod will pass the least possible amount of information Server Apache The answer you are probably looking for is how to make Apache lie about what what it is ie send something like Server Bob s Happy HTTPd Server In order to do this you will need to modify the Apache source code and rebuild Apache This is not advised as it is almost certain not to provide you with the added security you think that you are gaining The exact method of doing this is left as an exercise for the reader as we are not keen on helping you do something that is intrinsically a bad idea Why do I see requests for other sites appearing in my log files A an access log entry showing this situation could look like this 63 251 56 142 25 Jul 2002 12 48 04 0700 GET http www yahoo com HTTP 1 0 200 1456 The question is why did a request for www yahoo com come to your server instead of Yahoo s server And why does the response have a status code of 200 success This is usually the result of malicious clients trying to exploit open proxy servers to access a website without revealing their true location If you find entries like this in your log the first thing to do is to make sure you have properly configured your server not to proxy for unknown clients If you don t need to provide a proxy server at all you should simply assure that the ProxyRequests directive is not set on If you do need to run a proxy server then you must ensure that you secure your server properly so that only authorized clients can use it If your server is configured properly then the attempt to proxy through your server will fail If you see a status code of 404 file not found in the log then you know that the request failed If you see a status code of 200 success that does not necessarily mean that the attempt to proxy succeeded RFC2616 section 5 1 2 mandates that Apache must accept requests with absolute URLs in the request URI even for non proxy requests Since Apache has no way to know all the different names that your server may be known under it cannot simply reject hostnames it does not recognize Instead it will serve requests for unknown sites locally by stripping off the hostname and using the default server or virtual host Therefore you can compare the size of the file 1456 in the above example to the size of the corresponding file in your default server If they are the same then the proxy attempt failed since a document from your server was delivered not a document from www yahoo com If you wish to prevent this type of request entirely then you need to let Apache know what hostnames to accept and what hostnames to reject You do this

    Original URL path: http://www.faciliteursfinanciers.be/manual/misc/FAQ.html (2012-07-05)
    Open archived version from archive

  • Site Map
    Apache Server Frequently Asked Questions Guides Tutorials and HowTos Authentication Authorization and Access Control Apache Tutorial Dynamic Content with CGI Apache Tutorial Introduction to Server Side Includes HOWTO documentation Apache Tutorials Platform specific Notes Using Apache with Microsoft Windows Compiling Apache for Microsoft Windows Running Apache for Windows as a Service Using Apache with Cygwin The Apache EBCDIC Port The Apache TPF Port Installing Apache on TPF Using Apache with HP MPE iX Using Apache with Novell NetWare Compiling Apache under UnixWare Running a High Performance Web Server for BSD Performance Tuning Tips for Digital Unix Running a High Performance Web Server on HPUX Hints on Running a High Performance Web Server Apache HTTP Server and Supporting Programs Manual Page httpd Apache HTTP Server Manual Page apxs Apache HTTP Server Manual Page ab Apache HTTP Server Manual Page apachectl Apache HTTP Server Manual Page dbmmanage Apache HTTP Server Manual Page htdigest Apache HTTP Server Manual Page htpasswd Apache HTTP Server Manual Page logresolve Apache HTTP Server Manual Page rotatelogs Apache HTTP Server Manual Page suexec Apache HTTP Server Other Programs Apache HTTP Server Apache modules Apache modules By Type Apache directives Definitions of terms used to describe Apache directives Definitions of terms used to describe Apache modules Apache Core Features Apache module mod access Apache module mod actions Apache module mod alias Apache module mod asis Apache module mod auth Apache module mod auth anon c Apache module mod auth db Apache module mod auth dbm Apache module mod auth digest Apache module mod autoindex Apache module mod cern meta Apache module mod cgi Apache module mod digest Apache module mod dir Apache module mod env Apache module mod example Apache module mod expires Apache module mod headers Apache module mod imap Apache module mod include Apache module mod info

    Original URL path: http://www.faciliteursfinanciers.be/manual/sitemap.html (2012-07-05)
    Open archived version from archive

  • Apache directives
    Action AddAlt AddAltByEncoding AddAltByType AddCharset AddDefaultCharset AddDescription AddEncoding AddHandler AddIcon AddIconByEncoding AddIconByType AddLanguage AddModule AddModuleInfo AddType AgentLog Alias AliasMatch Allow AllowCONNECT AllowOverride Anonymous Anonymous Authoritative Anonymous LogEmail Anonymous MustGiveEmail Anonymous NoUserID Anonymous VerifyEmail AuthAuthoritative AuthDBAuthoritative AuthDBGroupFile AuthDBMAuthoritative AuthDBMGroupFile AuthDBMGroupFile AuthDBUserFile AuthDBMUserFile AuthDigestFile AuthGroupFile AuthName AuthType AuthUserFile BindAddress BrowserMatch BrowserMatchNoCase BS2000Account CacheDefaultExpire CacheDirLength CacheDirLevels CacheForceCompletion CacheGcInterval CacheLastModifiedFactor CacheMaxExpire CacheNegotiatedDocs CacheRoot CacheSize CGICommandArgs CheckSpelling ClearModuleList ContentDigest CookieDomain CookieExpires CookieFormat CookieLog mod cookies CookieLog mod log config CookiePrefix CookieStyle CookieTracking CoreDumpDirectory CustomLog DefaultIcon DefaultLanguage DefaultType Define Deny Directory DirectoryMatch DirectoryIndex DocumentRoot EBCDICConvert EBCDICConvertByType EBCDICKludge EnableExceptionHook ErrorDocument ErrorHeader ErrorLog Example ExpiresActive ExpiresByType ExpiresDefault ExtendedStatus FancyIndexing FileETag Files FilesMatch ForceType ForensicLog Group Header HeaderName HostnameLookups IdentityCheck IfDefine IfModule ImapBase ImapDefault ImapMenu Include IndexIgnore IndexOptions IndexOrderDefault ISAPIReadAheadBuffer ISAPILogNotSupported ISAPIAppendLogToErrors ISAPIAppendLogToQuery KeepAlive KeepAliveTimeout LanguagePriority Limit LimitExcept LimitInternalRecursion LimitRequestBody LimitRequestFields LimitRequestFieldsize LimitRequestLine Listen ListenBacklog LoadFile LoadModule Location LocationMatch LockFile LogFormat LogLevel MaxClients MaxKeepAliveRequests MaxRequestsPerChild MaxSpareServers MetaDir MetaFiles MetaSuffix MimeMagicFile MinSpareServers MMapFile NameVirtualHost NoCache Options Order PassEnv PidFile Port ProtocolReqCheck ProxyBlock ProxyDomain ProxyPass ProxyPassReverse ProxyReceiveBufferSize ProxyRemote ProxyRequests ProxyVia ReadmeName Redirect RedirectMatch RedirectPermanent RedirectTemp RefererIgnore RefererLog RemoveEncoding RemoveHandler RemoveType Require ResourceConfig RewriteBase RewriteCond RewriteEngine RewriteLock RewriteLog RewriteLogLevel RewriteMap RewriteOptions RewriteRule RLimitCPU RLimitMEM RLimitNPROC Satisfy ScoreBoardFile Script ScriptAlias ScriptAliasMatch ScriptInterpreterSource ScriptLog

    Original URL path: http://www.faciliteursfinanciers.be/manual/mod/directives.html (2012-07-05)
    Open archived version from archive

  • Apache modules
    authentication using DBM files mod auth digest Apache 1 3 8 and up MD5 authentication mod autoindex Automatic directory listings mod browser Apache 1 2 only Set environment variables based on User Agent strings Replaced by mod setenvif in Apache 1 3 and up mod cern meta Apache 1 1 and up Support for HTTP header metafiles mod cgi Invoking CGI scripts mod cookies up to Apache 1 1 1 Support for Netscape like cookies Replaced in Apache 1 2 by mod usertrack mod define Variable Definition for Arbitrary Directives mod digest Apache 1 1 and up MD5 authentication deprecated by mod auth digest mod dir Basic directory handling mod dld Apache 1 2 and earlier Start time linking with the GNU libdld Replaced in Apache 1 3 by mod so mod env Apache 1 1 and up Passing of environments to CGI scripts mod example Apache 1 2 and up Demonstrates Apache API mod expires Apache 1 2 and up Apply Expires headers to resources mod headers Apache 1 2 and up Add arbitrary HTTP headers to resources mod imap Apache 1 1 and up The imagemap file handler mod include Server parsed documents mod info Apache 1 1 and up Server configuration information mod isapi WIN32 only Windows ISAPI Extension support mod log agent Logging of User Agents mod log common up to Apache 1 1 1 Standard logging in the Common Logfile Format Replaced by the mod log config module in Apache 1 2 and up mod log config User configurable logging replacement for mod log common mod log forensic Forensic logging of requests made to the server mod log referer Logging of document references mod mime Determining document types using file extensions mod mime magic Determining document types using magic numbers mod mmap static Apache 1

    Original URL path: http://www.faciliteursfinanciers.be/manual/mod/ (2012-07-05)
    Open archived version from archive

  • New features with Apache 1.3
    it The identifier is available in the environment variable UNIQUE ID mod proxy enhancements Easier and safer authentication for ftp proxy logins When no ftp user name and or password is specified in the URL but the destination ftp server requires one Apache now returns a 401 Authorization Required status This status code usually makes the client browser pop up an Enter user name and password dialog and the request is retried with the given user authentification That is slightly more secure than specifying the authentication information as part of the request URL where it could be logged in plaintext by older proxy servers The new AllowCONNECT directive allows configuration of the port numbers to which the proxy CONNECT method may connect That allows proxying to https some server 8443 which resulted in an error message prior to Apache version 1 3 2 The proxy now supports the HTTP 1 1 Via header as specified in RFC2068 The new ProxyVia directive allows switching Via support off or on or suppressing outgoing Via header lines altogether for privacy reasons The Max Forwards TRACE header specified in HTTP 1 1 is now supported With it you can trace the path of a request along a chain of proxies if they too support it NoProxy and ProxyDomain directives added to proxy useful for intranets New ProxyPassReverse directive It lets Apache adjust the URL in the Location header on HTTP redirect responses Easier navigation in ftp server directory trees Enhanced mod include string comparisons The string based server side include SSI flow control directives now include comparison for less than less than or equal greater than and greater than or equal Previously comparisons could only be made for equality or inequality ServerRoot relative auth filenames Auth filenames for the various authentication modules are now treated as relative to the ServerRoot if they are not full paths Enhancements to directory indexing Code split The mod dir module has been split in two with mod dir handling directory index files and mod autoindex creating directory listings Thus allowing folks to remove the indexing function from critical servers Sortable Clicking on a column title will now sort the listing in order by the values in that column This feature can be disabled using the SuppressColumnSorting IndexOptions keyword SuppressHTMLPreamble can be used if your README html file includes its own HTML header The IndexOptions directive now allows the use of incremental prefixes to add remove the respective keyword feature as was already possible for the Options directive to its keyword arguments Multiple IndexOptions directives applying to the same directory will now be merged IconHeight and IconWidth let you set height and width attributes to the IMG tag in directory listings The new NameWidth keyword to the IndexOptions directive lets you set the number of columns for fancy directory listings If set to an asterisk the name width will be adjusted automatically The FancyIndexing directive now correctly has the same impact as IndexOptions FancyIndexing without replacing the effect of any existing IndexOptions directive Starting with 1 3 15 the server will satisfy directory requests with the cache controls ETag and LastModified if IndexOptions includes the TrackModified directive The server will not need to generate the listing if the client determines the request has not changed improving performance Due to its experimental nature this feature is not enabled by default Less Buffering of CGI Script Output In previous versions of Apache the output from CGI scripts would be internally buffered by the server and wouldn t be forwarded to the client until either the buffers were full or the CGI script completed As of Apache 1 3 the buffer to the client is flushed any time it contains something and the server is waiting for more information from the script This allows CGI script to provide partial status reports during long processing operations Regular Expression support for Alias and Redirect New AliasMatch ScriptAliasMatch and RedirectMatch directives allow for the use of regular expression matching Additionally new DirectoryMatch LocationMatch and FilesMatch sections provide a new syntax for regular expression sectioning AddModuleInfo directive added to mod info Allows additional information to be listed along with a specified module Absence of any TransferLog disables logging If no TransferLog directive is given then no log is written This supports co existence with other logging modules Ability to name logging formats The LogFormat directive has been enhanced to allow you to give nicknames to specific logging formats You can then use these nicknames in other LogFormat and CustomLog directives rather than having to spell out the complete log format string each time Conditional logging mod log config now supports logging based upon environment variables mod log referer and mod log agent are now deprecated mod cern meta configurable per directory mod cern meta is now configurable on a per directory basis New map types for RewriteMap directive The new map types Randomized Plain Text and Internal Function were added to the RewriteMap directive of mod rewrite They provide two new features First you now can randomly choose a sub value from a value which was looked up in a rewriting map which is useful when choosing between backend servers in a Reverse Proxy situation Second you now can translate URL parts to fixed upper or lower case which is useful when doing mass virtual hosting by the help of mod rewrite CIDR and Netmask access control mod access directives now support CIDR Classless Inter Domain Routing style prefixes and netmasks for greater control over IP access lists API Additions and Changes For all those module writers and code hackers child init A new phase for Apache s API is called once per heavy weight process before any requests are handled This allows the module to set up anything that need to be done once per processes For example connections to databases child exit A new phase called once per heavy weight process when it is terminating Note that it can t be called in some

    Original URL path: http://www.faciliteursfinanciers.be/manual/new_features_1_3.html (2012-07-05)
    Open archived version from archive



  •