From: brian Date: Sat, 6 Jun 1998 15:39:26 +0000 (+0000) Subject: PR: 2365 X-Git-Tag: 1.3.1~27 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=58139b66f83c958e6ef115be071b0af6369e1251;p=thirdparty%2Fapache%2Fhttpd.git PR: 2365 Updated certain questions for 1.3 - simplicity is always a good idea. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@81480 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/FAQ.html b/docs/manual/misc/FAQ.html index edab3e03a81..52439ba718e 100644 --- a/docs/manual/misc/FAQ.html +++ b/docs/manual/misc/FAQ.html @@ -14,7 +14,7 @@

Apache Server Frequently Asked Questions

- $Revision: 1.118 $ ($Date: 1998/05/30 01:27:25 $) + $Revision: 1.119 $ ($Date: 1998/06/06 15:39:26 $)

The latest version of this FAQ is always available from the main @@ -1091,19 +1091,15 @@

Apache does not send automatically send a cookie on every response, unless you have re-compiled it with the - mod_cookies - module. - This module was distributed with Apache prior to 1.2. - This module may help track users, and uses cookies to do this. If - you are not using the data generated by mod_cookies, do - not compile it into Apache. Note that in 1.2 this module was renamed - to the more correct name - mod_usertrack, - and cookies - have to be specifically enabled 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.

@@ -1245,59 +1241,16 @@ it? Why doesn't my server push work?

- In order to improve network performance, Apache buffers script output - into relatively large chunks. If you have a script that sends - information in bursts (eg. as partial-done messages in a multi-commit - database transaction or any type of server push), the client will - not necessarily get the output as the script is generating it. -

-

- To avoid this, Apache recognizes scripts whose names begin with - "nph-" as non-parsed-header scripts. - That is, Apache won't buffer their output, but connect it directly to - the socket going back to the client. -

-

- While this will probably do what you want, there are some - disadvantages to it: -

- -

- As an example how you might handle the former (in a Perl script): -

-

-

-
if ($0 =~ m:^(.*/)*nph-[^/]*$:) { -
-      - $HTTP_headers =  - "HTTP/1.1 200 OK\015\012"; -
-      - $HTTP_headers .=  - "Connection: close\015\012"; -
-      - print $HTTP_headers; -
- } -
-
-

-

- and then follow with your normal non-nph headers. + As of Apache 1.3, CGI scripts are essentially not buffered. Every time + your script does a "flush" to output data, that data gets relayed on to + the client. Some scripting languages, for example Perl, have their own + buffering for output - this can be disabled by setting the $! + special variable to 1. Of course this does increase the overall number + of packets being transmitted, which can result in a sense of slowness by + the end user.

-

Note that in version 1.3, all CGI scripts will be unbuffered - so the only difference between nph scripts and normal scripts is +

Prior to 1.3, you needed to use "nph-" scripts to accomplish non-buffering. + Today, the only difference between nph scripts and normal scripts is that nph scripts require the full HTTP headers to be sent.