Unofficial - F5 Certification Exam Prep Material > F5 N1-N4 - NGINX OSS - NOT CREATED Source | Edit on
F5N3 - Configuration: Demonstrate¶
TODO
Objective - 1.1 Demonstrate how to manage connections and bandwidth¶
1.1 - Demonstrate how to limit the amount of connections that are made to the NGINX server and its upstreams¶
TODO
1.1 - Understand how to enable and optimize keep-alives for the NGINX server and its upstreams¶
TODO
Objective - 1.2 Demonstrate how to restrict access¶
1.2 - Demonstrate how to authenticate (auth basic / auth request)¶
TODO
location / {
auth_basic "Private site";
auth_basic_user_file conf.d/passwd;
}
This example shows the / location being protected thanks to two directives.
auth_basic enables authentication by defining an HTTP Basic authentication
realm name (see RFC 2617 for more details).
auth_basic_user_file points to a user file (containing username and
password pairs) as defined here.
This allows to make sure that users accessing endpoints matching the location
/ {} must present valid authentication credentials following the HTTP Basic
authentication specification. Other users will be returned 401 or 403 error
codes.
On another hand, NGINX proposes another,