2008 February 26th Tuesday (二月 二十六日 火曜日)
2008-06-02 11:41
483 查看
Sometimes we may wish to avoid brower built-in authentication dialogs altogether. Since the dialog is automatically triggered
by an HTTP 401 or 407 response, we must avoid sending these codes to the client. It is not longer sufficient event to send a login
from as ErrorDocument. Instead, we must either (a) present the unauthenticated user with a login form immediately, or (b) redirect
the unauthenticated user to a login form with an HTTP 302 response.
Each filter chain (input and output) passes through predefined stages. Thus the same filter architecture can be used for different
kinds of operation. In brief, from the content generator to client, we have the following classes of filter:
Content filters, which process document contents within a request. These are the filter most commonly relevant to applications
programming.
Protocol filters, which deal with details of the protocol but treat the contents as opaque. These filters are concerned with translating
between HTTP data(as defined in RFC2616) and Apache's internal representation in the request_rec and associated structures.
Connection filter, which process a TCP connection without referentce to HTTP (either the protocol ot contents). These filters are
concerned with interfacing Apache with the network; they operate entirely outside the scope of HTTP or of any request_rec.
by an HTTP 401 or 407 response, we must avoid sending these codes to the client. It is not longer sufficient event to send a login
from as ErrorDocument. Instead, we must either (a) present the unauthenticated user with a login form immediately, or (b) redirect
the unauthenticated user to a login form with an HTTP 302 response.
Each filter chain (input and output) passes through predefined stages. Thus the same filter architecture can be used for different
kinds of operation. In brief, from the content generator to client, we have the following classes of filter:
Content filters, which process document contents within a request. These are the filter most commonly relevant to applications
programming.
Protocol filters, which deal with details of the protocol but treat the contents as opaque. These filters are concerned with translating
between HTTP data(as defined in RFC2616) and Apache's internal representation in the request_rec and associated structures.
Connection filter, which process a TCP connection without referentce to HTTP (either the protocol ot contents). These filters are
concerned with interfacing Apache with the network; they operate entirely outside the scope of HTTP or of any request_rec.
相关文章推荐
- 2008 February 19th Tuesday (二月 十九日 火曜日)
- 2008 February 5th Tuesday (二月 五日 火曜日
- 2008 August 26th Tuesday (八月 二十六日 火曜日)
- May 26th Tuesday (五月 二十六日 火曜日)
- February 10th Tuesday 2009 (二月 十日 火曜日)
- February 26th Thursday 2009 (二月 二十六日 木曜日)
- February 3rd Tuesday 2009 (二月 三日 火曜日)
- February 17th Tuesday 2009 (二月 十七日 火曜日)
- February 24th Tuesday 2009 (二月 二十四日 火曜日)
- June 26th Tuesday (六月 二十六日 火曜日)
- 2008 February 2nd Saturday (二月 二日 土曜日)
- 2008 February 28th Thursday (二月 二十八日 木曜日)
- 2008 March 11th Tuesday (三月 十一日 火曜日)
- 2008 February 18th Monday (二月 十八日 月曜日)
- 2008 February 29th Wednesday (二月 二十九日 金曜日)
- 2008 May 20th Tuesday (五月 二十日 火曜日)
- 2008 November 11th Tuesday (十一月 十一日 火曜日)
- 2008 October 28th Tuesday (十月 二十八日 火曜日)
- 2008 January 8th Tuesday (一月 八日 火曜日)
- 2008 January 22th Tuesday (一月 二十二日 火曜日)