archive-fr.com » FR » O » OBSPM.FR

Total: 155

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

Or switch to "Titles and links view".
  • mod_unique_id - Apache HTTP Server
    65536 values during a single second The quadruple ip addr pid time stamp counter is sufficient to enumerate 65536 requests per second per httpd process There are issues however with pid reuse over time and the counter is used to alleviate this issue When an httpd child is created the counter is initialized with current microseconds divided by 10 modulo 65536 this formula was chosen to eliminate some variance problems with the low order bits of the microsecond timers on some systems When a unique identifier is generated the time stamp used is the time the request arrived at the web server The counter is incremented every time an identifier is generated and allowed to roll over The kernel generates a pid for each process as it forks the process and pids are allowed to roll over they re 16 bits on many Unixes but newer systems have expanded to 32 bits So over time the same pid will be reused However unless it is reused within the same second it does not destroy the uniqueness of our quadruple That is we assume the system does not spawn 65536 processes in a one second interval it may even be 32768 processes on some Unixes but even this isn t likely to happen Suppose that time repeats itself for some reason That is suppose that the system s clock is screwed up and it revisits a past time or it is too far forward is reset correctly and then revisits the future time In this case we can easily show that we can get pid and time stamp reuse The choice of initializer for the counter is intended to help defeat this Note that we really want a random number to initialize the counter but there aren t any readily available numbers on most systems i e you can t use rand because you need to seed the generator and can t seed it with the time because time at least at one second resolution has repeated itself This is not a perfect defense How good a defense is it Suppose that one of your machines serves at most 500 requests per second which is a very reasonable upper bound at this writing because systems generally do more than just shovel out static files To do that it will require a number of children which depends on how many concurrent clients you have But we ll be pessimistic and suppose that a single child is able to serve 500 requests per second There are 1000 possible starting counter values such that two sequences of 500 requests overlap So there is a 1 5 chance that if time at one second resolution repeats itself this child will repeat a counter value and uniqueness will be broken This was a very pessimistic example and with real world values it s even less likely to occur If your system is such that it s still likely to occur then perhaps you should make the

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/mod_unique_id.html (2015-11-16)
    Open archived version from archive


  • mod_userdir - Apache HTTP Server
    off all username to directory translations except those explicitly named with the enabled keyword see below The keyword disabled followed by a space delimited list of usernames Usernames that appear in such a list will never have directory translation performed even if they appear in an enabled clause The keyword enabled followed by a space delimited list of usernames These usernames will have directory translation performed even if a global disable is in effect but not if they also appear in a disabled clause If neither the enabled nor the disabled keywords appear in the Userdir directive the argument is treated as a filename pattern and is used to turn the name into a directory specification A request for http www foo com bob one two html will be translated to UserDir directive used Translated path UserDir public html bob public html one two html UserDir usr web usr web bob one two html UserDir home www home bob www one two html The following directives will send redirects to the client UserDir directive used Translated path UserDir http www foo com users http www foo com users bob one two html UserDir http www foo com usr http www foo com bob usr one two html UserDir http www foo com http www foo com bob one two html Be careful when using this directive for instance UserDir would map root to which is probably undesirable It is strongly recommended that your configuration include a UserDir disabled root declaration See also the Directory directive and the Security Tips page for more information Additional examples To allow a few users to have UserDir directories but not anyone else use the following UserDir disabled UserDir enabled user1 user2 user3 To allow most users to have UserDir directories but deny this to

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/mod_userdir.html (2015-11-16)
    Open archived version from archive

  • mod_usertrack - Apache HTTP Server
    be useful True Netscape claims that the correct format NOW is four digit dates and four digit dates do in fact work for Netscape 4 x Communicator that is However 3 x and below do NOT accept them It seems that Netscape originally had a 2 digit standard and then with all of the Y2K hype and probably a few complaints changed to a four digit date for Communicator Fortunately 4 x also understands the 2 digit format and so the best way to ensure that your expiration date is legible to the client s browser is to use 2 digit dates However this does not limit expiration dates to the year 2000 if you use an expiration year of 13 for example it is interpreted as 2013 NOT 1913 In fact you can use an expiration year of up to 37 and it will be understood as 2037 by both MSIE and Netscape versions 3 x and up not sure about versions previous to those Not sure why Netscape used that particular year as its cut off point but my guess is that it was in respect to UNIX s 2038 problem Netscape MSIE 4 x seem to be able to understand 2 digit years beyond that at least until 50 for sure I think they understand up until about 70 but not for sure Summary Mozilla 3 x and up understands two digit dates up until 37 2037 Mozilla 4 x understands up until at least 50 2050 in 2 digit form but also understands 4 digit years which can probably reach up until 9999 Your best bet for sending a long life cookie is to send it for some time late in the year 37 CookieDomain Directive Description The domain to which the tracking cookie applies Syntax CookieDomain domain Context server config virtual host directory htaccess Override FileInfo Status Extension Module mod usertrack This directive controls the setting of the domain to which the tracking cookie applies If not present no domain is included in the cookie header field The domain string must begin with a dot and must include at least one embedded dot That is foo com is legal but foo bar com and com are not CookieExpires Directive Description Expiry time for the tracking cookie Syntax CookieExpires expiry period Context server config virtual host directory htaccess Override FileInfo Status Extension Module mod usertrack When used this directive sets an expiry time on the cookie generated by the usertrack module The expiry period can be given either as a number of seconds or in the format such as 2 weeks 3 days 7 hours Valid denominations are years months weeks days hours minutes and seconds If the expiry time is in any format other than one number indicating the number of seconds it must be enclosed by double quotes If this directive is not used cookies last only for the current browser session CookieName Directive Description Name of the tracking cookie Syntax CookieName token Default

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/mod_usertrack.html (2015-11-16)
    Open archived version from archive

  • mod_vhost_alias - Apache HTTP Server
    t present the dot must be present if and only if M is present The interpretation is as follows 0 the whole name 1 the first part 2 the second part 1 the last part 2 the penultimate part 2 the second and all subsequent parts 2 the penultimate and all preceding parts 1 and 1 the same as 0 If N or M is greater than the number of parts available a single underscore is interpolated Examples For simple name based virtual hosts you might use the following directives in your server configuration file UseCanonicalName Off VirtualDocumentRoot usr local apache vhosts 0 A request for http www example com directory file html will be satisfied by the file usr local apache vhosts www example com directory file html For a very large number of virtual hosts it is a good idea to arrange the files to reduce the size of the vhosts directory To do this you might use the following in your configuration file UseCanonicalName Off VirtualDocumentRoot usr local apache vhosts 3 2 1 2 2 2 3 2 A request for http www domain example com directory file html will be satisfied by the file usr local apache vhosts example com d o m domain directory file html A more even spread of files can be achieved by hashing from the end of the name for example VirtualDocumentRoot usr local apache vhosts 3 2 1 2 2 2 3 2 The example request would come from usr local apache vhosts example com n i a domain directory file html Alternatively you might use VirtualDocumentRoot usr local apache vhosts 3 2 1 2 2 2 3 2 4 The example request would come from usr local apache vhosts example com d o m ain directory file html For IP based virtual hosting you might use the following in your configuration file UseCanonicalName DNS VirtualDocumentRootIP usr local apache vhosts 1 2 3 4 docs VirtualScriptAliasIP usr local apache vhosts 1 2 3 4 cgi bin A request for http www domain example com directory file html would be satisfied by the file usr local apache vhosts 10 20 30 40 docs directory file html if the IP address of www domain example com were 10 20 30 40 A request for http www domain example com cgi bin script pl would be satisfied by executing the program usr local apache vhosts 10 20 30 40 cgi bin script pl If you want to include the character in a VirtualDocumentRoot directive but it clashes with a directive you can work around the problem in the following way VirtualDocumentRoot usr local apache vhosts 2 0 3 0 A request for http www domain example com directory file html will be satisfied by the file usr local apache vhosts domain example directory file html The LogFormat directives V and A are useful in conjunction with this module VirtualDocumentRoot Directive Description Dynamically configure the location of the document root for a given virtual

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/mod_vhost_alias.html (2015-11-16)
    Open archived version from archive

  • Terms Used to Describe Directives - Apache HTTP Server
    if a filename contains more than one dot each dot separated part of the filename following the first dot is an extension For example the filename file html en contains two extensions html and en For Apache directives you may specify extension s with or without the leading dot In addition extension s are not case sensitive MIME type A method of describing the format of a file which consists of a major format type and a minor format type separated by a slash as in text html env variable The name of an environment variable defined in the Apache configuration process Note this is not necessarily the same as an operating system environment variable See the environment variable documentation for more details Default If the directive has a default value i e if you omit it from your configuration entirely the Apache Web server will behave as though you set it to a particular value it is described here If there is no default value this section should say None Note that the default listed here is not necessarily the same as the value the directive takes in the default httpd conf distributed with the server Context This indicates where in the server s configuration files the directive is legal It s a comma separated list of one or more of the following values server config This means that the directive may be used in the server configuration files e g httpd conf but not within any VirtualHost or Directory containers It is not allowed in htaccess files at all virtual host This context means that the directive may appear inside VirtualHost containers in the server configuration files directory A directive marked as being valid in this context may be used inside Directory Location and Files containers in the server configuration files subject to the restrictions outlined in How Directory Location and Files sections work htaccess If a directive is valid in this context it means that it can appear inside per directory htaccess files It may not be processed though depending upon the overrides currently active The directive is only allowed within the designated context if you try to use it elsewhere you ll get a configuration error that will either prevent the server from handling requests in that context correctly or will keep the server from operating at all i e the server won t even start The valid locations for the directive are actually the result of a Boolean OR of all of the listed contexts In other words a directive that is marked as being valid in server config htaccess can be used in the httpd conf file and in htaccess files but not within any Directory or VirtualHost containers Override This directive attribute indicates which configuration override must be active in order for the directive to be processed when it appears in a htaccess file If the directive s context doesn t permit it to appear in htaccess files then no context will be

    Original URL path: http://ama09.obspm.fr/manual-2.0/mod/directive-dict.html (2015-11-16)
    Open archived version from archive

  • Frequently Asked Questions - Apache HTTP Server
    file permissions or the like The default location of the error log is usr local apache2 logs error log but see the ErrorLog directive in your config files for the location on your server Check the FAQ The latest version of the Apache Frequently Asked Questions list can always be found at the main Apache web site Check the Apache bug database Most problems that get reported to The Apache Group are recorded in the bug database Please check the existing reports open and closed before adding one If you find that your issue has already been reported please don t add a me too report If the original report isn t closed yet we suggest that you check it periodically You might also consider contacting the original submitter because there may be an email exchange going on about the issue that isn t getting recorded in the database Ask in a user support forum Apache has an active community of users who are willing to share their knowledge Participating in this community is usually the best and fastest way to get answers to your questions and problems Users mailing list USENET newsgroups comp infosystems www servers unix news google comp infosystems www servers ms windows news google comp infosystems www authoring cgi news google If all else fails report the problem in the bug database If you ve gone through those steps above that are appropriate and have obtained no relief then please do let the httpd developers know about the problem by logging a bug report If your problem involves the server crashing and generating a core dump please include a backtrace if possible As an example cd ServerRoot dbx httpd core dbx where Substitute the appropriate locations for your ServerRoot and your httpd and core files You

    Original URL path: http://ama09.obspm.fr/manual-2.0/faq/all_in_one.html (2015-11-16)
    Open archived version from archive

  • Support - Frequently Asked Questions - Apache HTTP Server
    ErrorLog directive in your config files for the location on your server Check the FAQ The latest version of the Apache Frequently Asked Questions list can always be found at the main Apache web site Check the Apache bug database Most problems that get reported to The Apache Group are recorded in the bug database Please check the existing reports open and closed before adding one If you find that your issue has already been reported please don t add a me too report If the original report isn t closed yet we suggest that you check it periodically You might also consider contacting the original submitter because there may be an email exchange going on about the issue that isn t getting recorded in the database Ask in a user support forum Apache has an active community of users who are willing to share their knowledge Participating in this community is usually the best and fastest way to get answers to your questions and problems Users mailing list USENET newsgroups comp infosystems www servers unix news google comp infosystems www servers ms windows news google comp infosystems www authoring cgi news google If all else fails report the problem

    Original URL path: http://ama09.obspm.fr/manual-2.0/faq/support.html (2015-11-16)
    Open archived version from archive

  • Error Messages - Frequently Asked Questions - Apache HTTP Server
    it is available in order to speed sending of responses Unfortunately on some systems Apache will detect the presence of sendfile at compile time even when it does not work properly This happens most frequently when using network or other non standard file system Symptoms of this problem include the above message in the error log and zero length responses to non zero sized files The problem generally occurs only

    Original URL path: http://ama09.obspm.fr/manual-2.0/faq/error.html (2015-11-16)
    Open archived version from archive



  •